Triple

T2933687
Position Surface form Disambiguated ID Type / Status
Subject Alt-Mariendorf E79213 entity
Predicate locatedIn P40 FINISHED
Object Mariendorf E79213 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: Mariendorf | Statement: [Alt-Mariendorf, locatedIn, Mariendorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mariendorf
Context triple: [Alt-Mariendorf, locatedIn, Mariendorf]
  • A. Wandlitz
    Wandlitz is a municipality in the German state of Brandenburg, known for its lakes, forests, and proximity to Berlin.
  • B. Langendorf
    Langendorf is a municipality in the canton of Solothurn in northwestern Switzerland.
  • C. Fürstenwalde
    Fürstenwalde is a town in eastern Germany’s Brandenburg region, known for its location on the River Spree and its historic churches and medieval architecture.
  • D. Alt-Mariendorf chosen
    Alt-Mariendorf is a Berlin U-Bahn station in the Mariendorf district that serves as the southern terminus of line U6.
  • E. Lippendorf
    Lippendorf is a village in Saxony, Germany, historically notable as the birthplace of Katharina von Bora, the wife of Martin Luther.
  • 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_69ad8b0fbab081908f6a61567c045d8d completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad983b65f881909b8b7d3dc5c224fd completed March 8, 2026, 3:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69b0fc6c2cc08190ab34973c3f33a34d completed March 11, 2026, 5:23 a.m.
Created at: March 8, 2026, 2:56 p.m.