Triple
T31011534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eldora Mountain Resort |
E790219
|
entity |
| Predicate | hasLodgingOnsite |
P125325
|
FINISHED |
| Object | limited or none |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: limited or none | Statement: [Eldora Mountain Resort, hasLodgingOnsite, limited or none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLodgingOnsite Context triple: [Eldora Mountain Resort, hasLodgingOnsite, limited or none]
-
A.
hasNoLodgingOnSite
Indicates that no lodging or accommodation facilities are available at the specified location or site.
-
B.
hasHotelsOnSite
Indicates that the subject location includes one or more hotels situated directly on its premises.
-
C.
hasDayLodge
Indicates that a location or facility includes or is associated with a day-use lodge building or area.
-
D.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
E.
hasOnsiteFeature
chosen
Indicates that one entity possesses or includes a particular feature that is physically present at its location or premises.
- F. None of above.
Provenance (3 batches)
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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 29, 2026, 8:57 p.m.