Triple

T17447121
Position Surface form Disambiguated ID Type / Status
Subject U.S. Route 24 E424813 entity
Predicate runsThroughCity P10456 FINISHED
Object Temperance, Michigan
Temperance, Michigan is an unincorporated community and census-designated place in Monroe County near the Ohio border, known as a residential suburb of Toledo.
E1797069 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: Temperance, Michigan | Statement: [U.S. Route 24, runsThroughCity, Temperance, Michigan]
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: Temperance, Michigan
Triple: [U.S. Route 24, runsThroughCity, Temperance, Michigan]
Generated description
Temperance, Michigan is an unincorporated community and census-designated place in Monroe County near the Ohio border, known as a residential suburb of Toledo.

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_69d889db0ba481908402409af3b37917 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e44ffc89e4819096372cc55b40cc3b completed April 19, 2026, 3:46 a.m.
NED1 Entity disambiguation (via context triple) batch_6a13111c61bc819080dbdc25ad57ac76 completed May 24, 2026, 2:54 p.m.
NEDg Description generation batch_6a13123f14008190a62775eea01bd2d4 completed May 24, 2026, 2:59 p.m.
NED2 Entity disambiguation (via description) batch_6a1313d9f1688190ab230c0c39167e27 completed May 24, 2026, 3:06 p.m.
Created at: April 10, 2026, 5:47 a.m.