Triple

T16378078
Position Surface form Disambiguated ID Type / Status
Subject Council of Ministers of the GDR E397727 entity
Predicate location P40 FINISHED
Object East Berlin E25341 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: East Berlin | Statement: [Council of Ministers of the GDR, location, East Berlin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: East Berlin
Context triple: [Council of Ministers of the GDR, location, East Berlin]
  • A. East Berlin chosen
    East Berlin was the Soviet-controlled eastern sector of Berlin that served as the capital of East Germany during the Cold War.
  • B. West Berlin
    West Berlin was the Western-aligned, enclave-like portion of Berlin surrounded by East Germany during the Cold War, symbolizing resistance to Soviet pressure and the division of Germany.
  • C. Berlin Ost
    Berlin Ost was the former name of Berlin Ostbahnhof, a major railway station in the eastern part of Berlin, Germany.
  • D. Berlin government district
    The Berlin government district is the central area of Germany’s capital that houses key federal institutions, including the Bundestag in the Reichstag building and the offices of the Chancellor.
  • E. Berlin
    Berlin is a major Ethereum network upgrade that introduced various gas cost optimizations and transaction processing improvements to enhance the blockchain’s efficiency and performance.
  • 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_69d87f2880b48190ae1a9673a3bbef80 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e319d97e00819094aa094f52a5a93e completed April 18, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00580fec0c8190b7fb73dbc637fb61 completed May 10, 2026, 10:04 a.m.
Created at: April 10, 2026, 5:08 a.m.