Triple
T22004572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee Pass route |
E543417
|
entity |
| Predicate | openedAsRailRoute |
P106928
|
FINISHED |
| Object | late 19th 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 19th century | Statement: [Tennessee Pass route, openedAsRailRoute, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsRailRoute Context triple: [Tennessee Pass route, openedAsRailRoute, late 19th century]
-
A.
openedAsRailStop
Indicates that an entity began operation or was first established specifically as a railway stop.
-
B.
openedAsRailroad
chosen
Indicates that a transportation line or route was originally inaugurated and operated as a railroad.
-
C.
openedAsRailTerminal
Indicates that a facility or location began operation specifically as a rail terminal when it first opened.
-
D.
openedAsElectrifiedRoute
Indicates that a transportation route was inaugurated already equipped with electrification, rather than being electrified at a later time.
-
E.
openedAsWagonRoad
Indicates that a route or path was originally established and used as a wagon road.
- 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_69e11e2c814c8190837d072789000486 |
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.