Triple

T13489395
Position Surface form Disambiguated ID Type / Status
Subject Bundesstraße 96 E318592 entity
Predicate passesNear P416 FINISHED
Object Eberswalde E237109 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: Eberswalde | Statement: [Bundesstraße 96, passesNear, Eberswalde]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eberswalde
Context triple: [Bundesstraße 96, passesNear, Eberswalde]
  • A. Eberswalde chosen
    Eberswalde is a town in northeastern Germany known for its industrial heritage and surrounding forests, located northeast of Berlin.
  • B. Uraniburgum
    Uraniburgum is the Latin name for Uraniborg, the famous late 16th-century astronomical observatory and research center established by Tycho Brahe on the island of Hven.
  • C. Johannisthal
    Johannisthal is a locality in the Berlin borough of Treptow-Köpenick, known historically for Germany’s first airfield and its early aviation activities.
  • D. Golm
    Golm is a hill on the island of Usedom in Germany, known both for its elevation and for the large World War II war cemetery located on its slopes.
  • E. Berlinghausen
    Berlinghausen is a village within the municipality of Möhnesee in North Rhine-Westphalia, Germany.
  • 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_69f7463b758c8190abc0dd2a049d751e completed May 3, 2026, 12:57 p.m.
Created at: April 9, 2026, 9:43 p.m.