Triple
T23546143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic, Tennessee and Ohio Railroad |
E577898
|
entity |
| Predicate | transportCorridor |
P3034
|
FINISHED |
| Object | North Carolina–Tennessee corridor |
—
|
NE NERFINISHED |
How this triple was built (3 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: North Carolina–Tennessee corridor | Statement: [Atlantic, Tennessee and Ohio Railroad, transportCorridor, North Carolina–Tennessee corridor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: North Carolina–Tennessee corridor Context triple: [Atlantic, Tennessee and Ohio Railroad, transportCorridor, North Carolina–Tennessee corridor]
-
A.
Atlanta–Charlotte–Raleigh–Richmond corridor
The Atlanta–Charlotte–Raleigh–Richmond corridor is a major southeastern U.S. urban and economic belt linking several large metropolitan areas along a key interstate route.
-
B.
Tyler–Jacksonville–Rusk corridor
The Tyler–Jacksonville–Rusk corridor is a regional transportation and economic corridor in East Texas linking the cities of Tyler, Jacksonville, and Rusk.
-
C.
Atlanta–Columbus corridor
The Atlanta–Columbus corridor is a major transportation and economic route in western Georgia that links the Atlanta metropolitan area with the city of Columbus and the communities in between.
-
D.
Atlanta–Athens corridor
The Atlanta–Athens corridor is a heavily traveled economic and transportation corridor in northeastern Georgia linking the Atlanta metropolitan area with the college town of Athens.
-
E.
Piedmont corridor
The Piedmont corridor is a passenger rail route in North Carolina connecting key cities such as Raleigh, Durham, Greensboro, and Charlotte.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: North Carolina–Tennessee corridor Target entity description: The North Carolina–Tennessee corridor is a regional rail and transportation route linking communities across the Appalachian region between North Carolina and Tennessee.
-
A.
Atlanta–Charlotte–Raleigh–Richmond corridor
The Atlanta–Charlotte–Raleigh–Richmond corridor is a major southeastern U.S. urban and economic belt linking several large metropolitan areas along a key interstate route.
-
B.
Tyler–Jacksonville–Rusk corridor
The Tyler–Jacksonville–Rusk corridor is a regional transportation and economic corridor in East Texas linking the cities of Tyler, Jacksonville, and Rusk.
-
C.
Atlanta–Columbus corridor
The Atlanta–Columbus corridor is a major transportation and economic route in western Georgia that links the Atlanta metropolitan area with the city of Columbus and the communities in between.
-
D.
Atlanta–Athens corridor
The Atlanta–Athens corridor is a heavily traveled economic and transportation corridor in northeastern Georgia linking the Atlanta metropolitan area with the college town of Athens.
-
E.
Piedmont corridor
The Piedmont corridor is a passenger rail route in North Carolina connecting key cities such as Raleigh, Durham, Greensboro, and Charlotte.
- F. None of above. chosen
Provenance (2 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aeca3a408190899989fc8175e9c5 |
completed | April 29, 2026, 7:10 a.m. |
Created at: April 17, 2026, 6:11 p.m.