Triple

T13489224
Position Surface form Disambiguated ID Type / Status
Subject Glienicke/Nordbahn E318588 entity
Predicate hasBorderWith P224 FINISHED
Object Hohen Neuendorf E392707 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: Hohen Neuendorf | Statement: [Glienicke/Nordbahn, hasBorderWith, Hohen Neuendorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hohen Neuendorf
Context triple: [Glienicke/Nordbahn, hasBorderWith, Hohen Neuendorf]
  • A. Hohen Neuendorf chosen
    Hohen Neuendorf is a town in the German state of Brandenburg, located just north of Berlin and known as a residential suburb with access to the capital.
  • B. Königs Wusterhausen
    Königs Wusterhausen is a town in the German state of Brandenburg, located southeast of Berlin and integrated into the capital’s commuter belt.
  • C. Jüterbog
    Jüterbog is a historic town in the German state of Brandenburg, known for its medieval architecture and long-standing cultural heritage.
  • D. Schönwalde
    Schönwalde is a locality within the municipality of Wandlitz in the state of Brandenburg, Germany.
  • E. Neu-Hohenschönhausen
    Neu-Hohenschönhausen is a residential locality in the northeast of Berlin, known for its large prefabricated housing estates and post-war urban development.
  • 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_69d806b6bfec819089222715b2e86c8e completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaf3cbe2081908c6792362c67c8f1 completed April 12, 2026, 2:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7b05a6d808190bae503b177816718 completed May 3, 2026, 8:30 p.m.
Created at: April 9, 2026, 9:43 p.m.