Triple
T20260819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 62 (Tennessee) |
E498828
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
TN 62
TN 62 is a Tennessee state highway that runs through the eastern part of the state, connecting communities such as Oak Ridge and Wartburg.
|
E1420141
|
NE FINISHED |
How this triple was built (4 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: TN 62 | Statement: [State Route 62 (Tennessee), abbreviation, TN 62]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TN 62 Context triple: [State Route 62 (Tennessee), abbreviation, TN 62]
-
A.
TN 35
TN 35 is a state highway in Tennessee that serves as a primary north–south transportation route through several communities in the eastern part of the state.
-
B.
TN 338
TN 338 is a state highway in Tennessee that serves as a local connector route within the state's road network.
-
C.
TN 160
TN 160 is a state highway in Tennessee that serves as a regional connector route, linking local communities and major roadways.
-
D.
TN-1
TN-1 is the standard postal-style abbreviation used to refer to Tennessee’s 1st congressional district in the U.S. House of Representatives.
-
E.
Tasso, Tennessee
Tasso, Tennessee is an unincorporated community in Bradley County known primarily as a small rural locality near Cleveland in southeastern Tennessee.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: TN 62 Triple: [State Route 62 (Tennessee), abbreviation, TN 62]
Generated description
TN 62 is a Tennessee state highway that runs through the eastern part of the state, connecting communities such as Oak Ridge and Wartburg.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: TN 62 Target entity description: TN 62 is a Tennessee state highway that runs through the eastern part of the state, connecting communities such as Oak Ridge and Wartburg.
-
A.
TN 35
TN 35 is a state highway in Tennessee that serves as a primary north–south transportation route through several communities in the eastern part of the state.
-
B.
TN 338
TN 338 is a state highway in Tennessee that serves as a local connector route within the state's road network.
-
C.
TN 160
TN 160 is a state highway in Tennessee that serves as a regional connector route, linking local communities and major roadways.
-
D.
TN-1
TN-1 is the standard postal-style abbreviation used to refer to Tennessee’s 1st congressional district in the U.S. House of Representatives.
-
E.
Tasso, Tennessee
Tasso, Tennessee is an unincorporated community in Bradley County known primarily as a small rural locality near Cleveland in southeastern Tennessee.
- F. None of above. chosen
Provenance (5 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674ca77c081909cd2f44ccfe3662d |
completed | April 20, 2026, 6:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a08552e62a08190af0bf7605bc6b6b7 |
completed | May 16, 2026, 11:29 a.m. |
| NEDg | Description generation | batch_6a0855ea027481908eebd5cff8ac97fb |
completed | May 16, 2026, 11:32 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a08568fa1748190b4e2c21fc3ec0b63 |
completed | May 16, 2026, 11:35 a.m. |
Created at: April 11, 2026, 11:41 p.m.