Triple

T22469141
Position Surface form Disambiguated ID Type / Status
Subject DeKalb County, Tennessee E555441 entity
Predicate hasMajorHighway P385 FINISHED
Object State Route 96
State Route 96 is a Tennessee state highway that runs across multiple counties, serving as an important regional connector in the central part of the state.
E2288808 NE 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: State Route 96 | Statement: [DeKalb County, Tennessee, hasMajorHighway, State Route 96]
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: State Route 96
Triple: [DeKalb County, Tennessee, hasMajorHighway, State Route 96]
Generated description
State Route 96 is a Tennessee state highway that runs across multiple counties, serving as an important regional connector in the central part of the state.

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_69e11e52c2048190952dc5df209b9bed completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15bdeae9c8190a5b66e540484db37 completed April 29, 2026, 1:16 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5ae04a038081909a0fb90de913f6f5 completed July 18, 2026, 2:09 a.m.
NEDg Description generation batch_6a5ae13ba064819082e6e6c39e5a67ff completed July 18, 2026, 2:13 a.m.
NED2 Entity disambiguation (via description) batch_6a5ae1706b388190af6a5eca5d60c132 completed July 18, 2026, 2:14 a.m.
Created at: April 16, 2026, 8:48 p.m.