Triple
T31433694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ET&WNC Railroad corridor |
E801865
|
entity |
| Predicate | terminusHistoric |
P39746
|
FINISHED |
| Object | Johnson City, Tennessee |
—
|
NE NERFINISHED |
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: Johnson City, Tennessee | Statement: [ET&WNC Railroad corridor, terminusHistoric, Johnson City, Tennessee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusHistoric Context triple: [ET&WNC Railroad corridor, terminusHistoric, Johnson City, Tennessee]
-
A.
historicalTerminus
chosen
Indicates that one entity serves as the historically recognized endpoint or final limit of another entity, such as a route, period, or process.
-
B.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
C.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
D.
terminusEast
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
-
E.
terminusDescription
Indicates the textual description that characterizes the endpoint or final stop of a route, path, or process.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 30, 2026, 8:59 p.m.