Triple

T16984208
Position Surface form Disambiguated ID Type / Status
Subject Niederschönhausen E412020 entity
Predicate hasNeighbouringDistrict P17964 FINISHED
Object Blankenfelde E393553 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: Blankenfelde | Statement: [Niederschönhausen, hasNeighbouringDistrict, Blankenfelde]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Blankenfelde
Context triple: [Niederschönhausen, hasNeighbouringDistrict, Blankenfelde]
  • A. Blankenfelde
    Blankenfelde is a locality on the southern outskirts of Berlin, Germany, known for its suburban residential character and proximity to both the capital and surrounding Brandenburg countryside.
  • B. Blankenfelde chosen
    Blankenfelde is a locality within the Berlin borough of Pankow, known for its residential character and proximity to green spaces.
  • C. Marienfelde
    Marienfelde is a locality in the southern part of Berlin known for its residential areas and historical refugee reception center.
  • D. Blankenburg
    Blankenburg is a locality in the borough of Pankow in Berlin, Germany, known for its residential character and village-like atmosphere.
  • E. Blankenburg
    Blankenburg is a town in central Germany, located in the Harz region of the state of Saxony-Anhalt.
  • 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_69d886ca8f348190812768ea8d5055ce completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d18a0bf881908c449f499eb86495 completed April 18, 2026, 6:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00dc0f13c88190b55da5be40a0a476 completed May 10, 2026, 7:27 p.m.
Created at: April 10, 2026, 5:32 a.m.