Triple

T21343760
Position Surface form Disambiguated ID Type / Status
Subject Frio County, Texas E526271 entity
Predicate hasHighway P385 FINISHED
Object State Highway 85
State Highway 85 is a Texas state highway that runs through South Texas, connecting several rural communities and serving as a regional transportation route.
E2293180 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 Highway 85 | Statement: [Frio County, Texas, hasHighway, State Highway 85]
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 Highway 85
Triple: [Frio County, Texas, hasHighway, State Highway 85]
Generated description
State Highway 85 is a Texas state highway that runs through South Texas, connecting several rural communities and serving as a regional transportation route.

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_69e0b51c33048190ab27cede74ef798c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8a8515bc48190b79f80e505550cd5 completed April 22, 2026, 10:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a7a743fbbf48190bb304fe65a83f715 completed Aug. 11, 2026, 1 a.m.
NEDg Description generation batch_6a7a748c233481908b488686e4b1173d completed Aug. 11, 2026, 1:02 a.m.
NED2 Entity disambiguation (via description) batch_6a7a75154c448190b685993935fd348f completed Aug. 11, 2026, 1:04 a.m.
Created at: April 16, 2026, 4:44 p.m.