Triple
T22004659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durango and Silverton Narrow Gauge Railroad |
E543419
|
entity |
| Predicate | touristOperationBegan |
P140799
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Durango and Silverton Narrow Gauge Railroad, touristOperationBegan, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristOperationBegan Context triple: [Durango and Silverton Narrow Gauge Railroad, touristOperationBegan, late 20th century]
-
A.
tourismStartPeriod
chosen
Indicates the time period or date when a tourism-related activity, season, or service begins.
-
B.
operatesTouristAttraction
Indicates that an entity manages and runs the day-to-day operations of a tourist attraction.
-
C.
tourOpened
Indicates that a tour has begun or been made available for participation or viewing.
-
D.
touristAccess
Indicates that a place or resource is available for use or visitation by tourists.
-
E.
openedAsTouristSite
Indicates that a place or structure has been made accessible and designated for visitation by tourists.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1276d81e4819083a40e51249e7fd7 |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:20 p.m.