Triple
T13332930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee State Route 35 |
E317616
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
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.
|
E1035426
|
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 35 | Statement: [Tennessee State Route 35, abbreviation, TN 35]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TN 35 Context triple: [Tennessee State Route 35, abbreviation, TN 35]
-
A.
TN 160
TN 160 is a state highway in Tennessee that serves as a regional connector route, linking local communities and major roadways.
-
B.
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.
-
C.
TN-5
TN-5 is the commonly used abbreviation for Tennessee's 5th congressional district, a U.S. House of Representatives district centered around Nashville.
-
D.
Tasso, Tennessee
Tasso, Tennessee is an unincorporated community in Bradley County known primarily as a small rural locality near Cleveland in southeastern Tennessee.
-
E.
TN
TN is a UK postcode area covering Tunbridge Wells and surrounding parts of Kent and East Sussex.
- 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 35 Triple: [Tennessee State Route 35, abbreviation, TN 35]
Generated description
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.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: TN 35 Target entity description: 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.
-
A.
TN 160
TN 160 is a state highway in Tennessee that serves as a regional connector route, linking local communities and major roadways.
-
B.
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.
-
C.
TN-5
TN-5 is the commonly used abbreviation for Tennessee's 5th congressional district, a U.S. House of Representatives district centered around Nashville.
-
D.
Tasso, Tennessee
Tasso, Tennessee is an unincorporated community in Bradley County known primarily as a small rural locality near Cleveland in southeastern Tennessee.
-
E.
TN
TN is a UK postcode area covering Tunbridge Wells and surrounding parts of Kent and East Sussex.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f71f36e4cc819093007404ceb5da31 |
completed | May 3, 2026, 10:11 a.m. |
| NEDg | Description generation | batch_69f72126765481908ef6e6ae7349bd30 |
completed | May 3, 2026, 10:19 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69f7221887208190ac98945a023bc496 |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 9, 2026, 9:30 p.m.