Triple

T32597385
Position Surface form Disambiguated ID Type / Status
Subject Moody County E833256 entity
Predicate hasMajorHighway P385 FINISHED
Object South Dakota Highway 32
South Dakota Highway 32 is a state highway in eastern South Dakota that serves as an important east–west route through Moody County and nearby rural communities.
E2067210 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: South Dakota Highway 32 | Statement: [Moody County, hasMajorHighway, South Dakota Highway 32]
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: South Dakota Highway 32
Triple: [Moody County, hasMajorHighway, South Dakota Highway 32]
Generated description
South Dakota Highway 32 is a state highway in eastern South Dakota that serves as an important east–west route through Moody County and nearby rural communities.

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_69f3492ab63c8190aec24d5003b47c29 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c695d31c8190bbd496755c70c81a completed May 3, 2026, 3:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36655640e88190a9a631558cf2651a completed June 20, 2026, 10:03 a.m.
NEDg Description generation batch_6a366626e0708190b7b11d854a951965 completed June 20, 2026, 10:06 a.m.
NED2 Entity disambiguation (via description) batch_6a3666c5937c8190a41f48157f47f8dc completed June 20, 2026, 10:09 a.m.
Created at: May 1, 2026, 1:05 a.m.