Triple

T32069818
Position Surface form Disambiguated ID Type / Status
Subject Cheboygan River E818977 entity
Predicate hasBridge P386 FINISHED
Object State Street bridge in Cheboygan
The State Street bridge in Cheboygan is a key vehicular crossing and local landmark spanning the Cheboygan River in Cheboygan, Michigan.
E1991413 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 Street bridge in Cheboygan | Statement: [Cheboygan River, hasBridge, State Street bridge in Cheboygan]
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 Street bridge in Cheboygan
Triple: [Cheboygan River, hasBridge, State Street bridge in Cheboygan]
Generated description
The State Street bridge in Cheboygan is a key vehicular crossing and local landmark spanning the Cheboygan River in Cheboygan, Michigan.

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_69f348fecc088190af1470afe5a969f0 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b526352081909d71322d026fbac5 completed May 3, 2026, 2:38 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2edde51a4481908b9bf7179c74ae43 completed June 14, 2026, 4:59 p.m.
NEDg Description generation batch_6a2edf10d3e08190ba2869891314532a completed June 14, 2026, 5:04 p.m.
NED2 Entity disambiguation (via description) batch_6a2ee07c3fd8819087148aa1c1ca6c43 completed June 14, 2026, 5:10 p.m.
Created at: May 1, 2026, 12:23 a.m.