Triple

T3410291
Position Surface form Disambiguated ID Type / Status
Subject Alexandrowka colony E71874 entity
Predicate isManagedBy P86 FINISHED
Object City of Potsdam E13693 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: City of Potsdam | Statement: [Alexandrowka colony, isManagedBy, City of Potsdam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: City of Potsdam
Context triple: [Alexandrowka colony, isManagedBy, City of Potsdam]
  • A. Potsdam chosen
    Potsdam is a historic German city near Berlin, known for its palaces, parks, and role in major 20th-century diplomatic events.
  • B. Lippendorf
    Lippendorf is a village in Saxony, Germany, historically notable as the birthplace of Katharina von Bora, the wife of Martin Luther.
  • C. Brandenburg an der Havel
    Brandenburg an der Havel is a historic town in eastern Germany, considered one of the cradles of the state of Brandenburg and known for its medieval architecture and waterways.
  • D. Wandlitz
    Wandlitz is a municipality in the German state of Brandenburg, known for its lakes, forests, and proximity to Berlin.
  • E. Spandau
    Spandau is a western borough of Berlin, Germany, known for its historic old town, fortress, and role as an important residential and industrial district.
  • 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_69ad85ac312481909e7027ced1456a9f completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb9094b2881909262e58a470ed9d0 completed March 8, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69b503d6cd9c81908acb288091503ec1 completed March 14, 2026, 6:44 a.m.
Created at: March 8, 2026, 3:15 p.m.