Triple

T10333762
Position Surface form Disambiguated ID Type / Status
Subject Garden Kingdom of Dessau-Wörlitz E242943 entity
Predicate locatedNear P294 FINISHED
Object Dessau E102721 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: Dessau | Statement: [Garden Kingdom of Dessau-Wörlitz, locatedNear, Dessau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dessau
Context triple: [Garden Kingdom of Dessau-Wörlitz, locatedNear, 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 (3 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_69d381af787481908bc401325c760a88 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4dfc366b481909c49f199892e9d42 completed April 7, 2026, 10:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69deb028c0788190ae8d6750f2f9634e completed April 14, 2026, 9:22 p.m.
Created at: April 6, 2026, 11:53 a.m.