Triple
T30677050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenwood Inn (historic hotel site) |
E780940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former lodging establishment |
C24231
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: former lodging establishment Context triple: [Greenwood Inn (historic hotel site), instanceOf, former lodging establishment]
-
A.
former coaching inn
A former coaching inn is a historic roadside lodging and service establishment, once used to accommodate travelers and horses on long-distance coach routes, that has since ceased its original coaching function and may now serve a different purpose.
-
B.
former resort
A former resort is a once-operational vacation or leisure property that has ceased functioning in its original capacity, often repurposed, abandoned, or left in partial use.
-
C.
site of former hotel
chosen
A site of former hotel is a location where a hotel once stood but has since been demolished, repurposed, or otherwise ceased to function as a hotel, leaving only the place and its historical association.
-
D.
former hunting lodge
A former hunting lodge is a building originally constructed as a rural retreat for hunting activities, later repurposed for other residential or recreational uses.
-
E.
historic boarding house
A historic boarding house is a long-standing residential building that once provided affordable, communal lodging—often with shared meals and services—to transient workers, travelers, or long-term tenants, reflecting the social and architectural character of its era.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:32 p.m.