Triple
T22004658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durango and Silverton Narrow Gauge Railroad |
E543419
|
entity |
| Predicate | lineOpened |
P37968
|
FINISHED |
| Object | 1882 |
—
|
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: 1882 | Statement: [Durango and Silverton Narrow Gauge Railroad, lineOpened, 1882]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineOpened Context triple: [Durango and Silverton Narrow Gauge Railroad, lineOpened, 1882]
-
A.
lineBOpened
Indicates that a specific line B has been opened or activated, transitioning from a closed or inactive state.
-
B.
openingLineStatus
Indicates the status or condition of an entity’s opening line, such as whether it exists, is valid, or meets a specified criterion.
-
C.
originalLineOpened
chosen
Indicates that a transportation or service line began its initial operation or was first opened for use.
-
D.
lineStatus
Indicates the current operational or functional state of a line or connection within a system.
-
E.
lineAPlatformOpened
Indicates that the platform associated with line A has been opened and is now available for use.
- 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.