Triple

T19925995
Position Surface form Disambiguated ID Type / Status
Subject Owensboro metropolitan area E478922 entity
Predicate hasMajorHighway P385 FINISHED
Object U.S. Route 1440
U.S. Route 1440 is a major United States highway serving the Owensboro metropolitan area in Kentucky, facilitating regional connectivity and transportation.
E2032537 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: U.S. Route 1440 | Statement: [Owensboro metropolitan area, hasMajorHighway, U.S. Route 1440]
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: U.S. Route 1440
Triple: [Owensboro metropolitan area, hasMajorHighway, U.S. Route 1440]
Generated description
U.S. Route 1440 is a major United States highway serving the Owensboro metropolitan area in Kentucky, facilitating regional connectivity and transportation.

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_69d8e521855c8190b41871700afc8d6a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e659c992fc8190bd262d528be0e636 completed April 20, 2026, 4:52 p.m.
NED1 Entity disambiguation (via context triple) batch_6a34da960dac81909237caf8379f94d8 completed June 19, 2026, 5:58 a.m.
NEDg Description generation batch_6a34db8b54248190bbae5ab7444e5a08 completed June 19, 2026, 6:02 a.m.
NED2 Entity disambiguation (via description) batch_6a34dc8ff0b48190a6a9561683f13215 completed June 19, 2026, 6:07 a.m.
Created at: April 10, 2026, 1:53 p.m.