Triple

T18133127
Position Surface form Disambiguated ID Type / Status
Subject Battle of Dessau Bridge E434065 entity
Predicate hasLocation P40 FINISHED
Object Dessau NE NERFINISHED

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: Dessau | Statement: [Battle of Dessau Bridge, hasLocation, Dessau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dessau
Context triple: [Battle of Dessau Bridge, hasLocation, Dessau]
  • A. Dessau chosen
    Dessau is a German city best known for its association with the Bauhaus movement and its iconic modernist architecture.
  • B. Oranienburg
    Oranienburg is a town in Brandenburg, Germany, historically known as the site of the Nazi Sachsenhausen concentration camp.
  • C. Degendorf
    Degendorf is a locality within the Bavarian town and district of Lichtenfels in Germany.
  • D. Sangerhausen
    Sangerhausen is a town in the German state of Saxony-Anhalt, known for its historic mining heritage and its renowned Europa-Rosarium rose garden.
  • E. Riedenburg
    Riedenburg is a small Bavarian town in southern Germany known for its scenic location in the Altmühl Valley and its historic castles.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b909e8cc81908df4cc2b8ea6d11f completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4de04321c81909c0b9d47757720fd completed April 19, 2026, 1:52 p.m.
Created at: April 10, 2026, 10:29 a.m.