Triple

T17770724
Position Surface form Disambiguated ID Type / Status
Subject Breite Straße E443628 entity
Predicate locatedIn P40 FINISHED
Object Cölln NE NERFINISHED

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: Cölln | Statement: [Breite Straße, locatedIn, Cölln]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cölln
Context triple: [Breite Straße, locatedIn, Cölln]
  • A. Cölln chosen
    Cölln was a historic town on the River Spree that, together with Berlin, formed the core of what later became the city of Berlin.
  • B. Falkensee
    Falkensee is a town in the Havelland district of Brandenburg, Germany, situated just west of Berlin and functioning largely as a residential suburb of the capital.
  • C. Grevesmühlen
    Grevesmühlen is a small town in the German state of Mecklenburg-Vorpommern, known as a local administrative and service center in the north of the country.
  • D. Brühl
    Brühl is a German town in North Rhine-Westphalia known for its historic architecture and as the birthplace of surrealist artist Max Ernst.
  • E. Luisenstadt
    Luisenstadt is a historic former district of Berlin, Germany, known for its 19th-century urban development and significant cultural and architectural heritage.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9edf16c8190a59ebd245d378f4f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e485ff928481909fe32260ba57978f completed April 19, 2026, 7:36 a.m.
Created at: April 10, 2026, 10:11 a.m.