HotelHinge · Method
How HotelHinge builds these pages
Each page that answers who owns a hotel is written by HotelHinge's own code from facts in its database. The facts come from public news reports of hotel sales and from county property records. No page copies or quotes a source, and no page names a private person.
Where do the facts come from?
HotelHinge reads public reports of U.S. hotel sales every day and keeps the basic facts of each one: the hotel, its city and state, the buyer, the seller, the price, and when and where the sale was reported. Some pages draw on county property records instead, which list who bought a property, when, and for how much.
How is each fact checked?
One model reads the report and pulls out each fact with the sentence it came from. A second model, run separately, checks every fact against that sentence. A fact is shown only when the check agrees, and a sale is shown only when nothing about it is under review or in dispute. Code then builds the page and checks it before it goes live: no text copied from a source, no person's name, no number that is not in the record.
What does a page show?
The hotel, its city and state, the buyer, the seller, the price, and when and by whom the sale was reported. Anything the reports do not say is stated as unknown, never guessed. The date at the top of each page is the last time its facts changed.
What does a page never show?
No photos or images, no quotes, no text taken from a report, no link to a paywalled article, and no private person's name. HotelHinge members see each sale's full record and its sources in the app.
How do pages go live?
A sale gets its page at least 72 hours after it was first reported. New pages are added a few at a time, and a sample of published pages is checked against the database again before more are added.
What if a page is wrong?
Write to info@hotelhinge.com with the page address. We hide the page within one business day while we check it, reply within two, and correct, restore or keep it hidden within ten. The process is in our Terms.