Triple

T29141910
Position Surface form Disambiguated ID Type / Status
Subject Lörick E738658 entity
Predicate hasTransportConnection P845 FINISHED
Object Rheinbrücke Theodor-Heuss-Brücke
Rheinbrücke Theodor-Heuss-Brücke is a major Rhine River bridge in Düsseldorf, Germany, serving as an important road link between the districts on either side of the river.
E1859912 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: Rheinbrücke Theodor-Heuss-Brücke | Statement: [Lörick, hasTransportConnection, Rheinbrücke Theodor-Heuss-Brücke]
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: Rheinbrücke Theodor-Heuss-Brücke
Triple: [Lörick, hasTransportConnection, Rheinbrücke Theodor-Heuss-Brücke]
Generated description
Rheinbrücke Theodor-Heuss-Brücke is a major Rhine River bridge in Düsseldorf, Germany, serving as an important road link between the districts on either side of the river.

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_69f07cb3adb48190a9e0e169cd026634 completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f6626fc3088190970ae48003cf2bf5 completed May 2, 2026, 8:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25890c1b748190824ba7c8a4d68615 completed June 7, 2026, 3:06 p.m.
NEDg Description generation batch_6a25944a643c8190b5458a00aa75a9fc completed June 7, 2026, 3:54 p.m.
NED2 Entity disambiguation (via description) batch_6a25949da2f88190bab7ab9362f3c3d8 completed June 7, 2026, 3:56 p.m.
Created at: April 28, 2026, 11:37 a.m.