Triple

T24553433
Position Surface form Disambiguated ID Type / Status
Subject Alabama State Route 133 E607439 entity
Predicate crossesVia P416 FINISHED
Object Singing River Bridge
The Singing River Bridge is a major highway bridge in Alabama that carries traffic across the Tennessee River near Muscle Shoals.
 E1808419 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: Singing River Bridge | Statement: [Alabama State Route 133, crossesVia, Singing River Bridge]
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: Singing River Bridge
Triple: [Alabama State Route 133, crossesVia, Singing River Bridge]
Generated description
The Singing River Bridge is a major highway bridge in Alabama that carries traffic across the Tennessee River near Muscle Shoals.

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_69e2c4cae1b88190825e88d5ce8aa61e completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a8cf1ef88190977da0fb79796616 completed April 30, 2026, 12:56 a.m.
NED1 Entity disambiguation (via context triple) batch_6a15e6788dd48190b122dc1cf3e5fb80 completed May 26, 2026, 6:29 p.m.
NEDg Description generation batch_6a15e86ccd388190957f409945ee75ed completed May 26, 2026, 6:37 p.m.
NED2 Entity disambiguation (via description) batch_6a15f0ae62c0819084cc22673b230c1b completed May 26, 2026, 7:12 p.m.
Created at: April 18, 2026, 2:27 a.m.