Triple

T15946806
Position Surface form Disambiguated ID Type / Status
Subject Alz E386705 entity
Predicate hasBridge P386 FINISHED
Object Alzbrücke Seebruck
Alzbrücke Seebruck is a bridge in Seebruck, Bavaria, that spans the river Alz near the northern shore of Lake Chiemsee.
 E1193895 NE FINISHED

How this triple was built (4 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: Alzbrücke Seebruck | Statement: [Alz, hasBridge, Alzbrücke Seebruck]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Alzbrücke Seebruck
Context triple: [Alz, hasBridge, Alzbrücke Seebruck]
  • A. Aspernbrücke
    Aspernbrücke is a bridge in Vienna, Austria, known for carrying traffic across the Danube Canal near the city center.
  • B. Boschbrücke
    Boschbrücke is a bridge in Munich, Germany, that connects to the Museumsinsel (Museum Island) over the Isar River.
  • C. Schlossbrücke
    Schlossbrücke is a historic bridge in central Berlin that spans the Spree River, connecting Unter den Linden with Museum Island near the Berlin Palace.
  • D. Herdbrücke
    Herdbrücke is a historic bridge in Ulm, Germany, spanning the Danube and connecting the city center with the neighboring town of Neu-Ulm.
  • E. Alte Brücke
    Alte Brücke is a historic stone bridge in Saarbrücken, Germany, known as one of the city’s oldest architectural landmarks spanning the Saar River.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Alzbrücke Seebruck
Triple: [Alz, hasBridge, Alzbrücke Seebruck]
Generated description
Alzbrücke Seebruck is a bridge in Seebruck, Bavaria, that spans the river Alz near the northern shore of Lake Chiemsee.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Alzbrücke Seebruck
Target entity description: Alzbrücke Seebruck is a bridge in Seebruck, Bavaria, that spans the river Alz near the northern shore of Lake Chiemsee.
  • A. Aspernbrücke
    Aspernbrücke is a bridge in Vienna, Austria, known for carrying traffic across the Danube Canal near the city center.
  • B. Boschbrücke
    Boschbrücke is a bridge in Munich, Germany, that connects to the Museumsinsel (Museum Island) over the Isar River.
  • C. Schlossbrücke
    Schlossbrücke is a historic bridge in central Berlin that spans the Spree River, connecting Unter den Linden with Museum Island near the Berlin Palace.
  • D. Herdbrücke
    Herdbrücke is a historic bridge in Ulm, Germany, spanning the Danube and connecting the city center with the neighboring town of Neu-Ulm.
  • E. Alte Brücke
    Alte Brücke is a historic stone bridge in Saarbrücken, Germany, known as one of the city’s oldest architectural landmarks spanning the Saar River.
  • F. None of above. chosen

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_69d86da882448190a82ea962fe343b79 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e156d1a4c08190afc325491ba38870 completed April 16, 2026, 9:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffeb82a29081909ef0e2685d0705c3 completed May 10, 2026, 2:20 a.m.
NEDg Description generation batch_69ffec4898088190bed531e33418c7e5 completed May 10, 2026, 2:24 a.m.
NED2 Entity disambiguation (via description) batch_69ffecce96508190a53f100e3207ebac completed May 10, 2026, 2:26 a.m.
Created at: April 10, 2026, 4:53 a.m.