Triple

T18987841
Position Surface form Disambiguated ID Type / Status
Subject Tennessee State Route System E464601 entity
Predicate hasNotableRoute P13417 FINISHED
Object State Route 52
State Route 52 is a significant east–west state highway in Tennessee that connects multiple rural communities across the northern part of the state.
 E2230244 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 52 | Statement: [Tennessee State Route System, hasNotableRoute, State Route 52]
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 52
Triple: [Tennessee State Route System, hasNotableRoute, State Route 52]
Generated description
State Route 52 is a significant east–west state highway in Tennessee that connects multiple rural communities across the northern 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_69d8dd008af48190a97ff1c6488edf1b completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6618ab881909c0ed94930e42e68 completed April 20, 2026, 7:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a4095112da0819085acc4ac3a99964f completed June 28, 2026, 3:29 a.m.
NEDg Description generation batch_6a4095bdb4888190a1bcbff88282e74c completed June 28, 2026, 3:32 a.m.
NED2 Entity disambiguation (via description) batch_6a40965a4a9881909930cd6dc75e1892 completed June 28, 2026, 3:34 a.m.
Created at: April 10, 2026, 12:01 p.m.