Triple

T43870
Position Surface form Disambiguated ID Type / Status
Subject West Germany E862 entity
Predicate deFactoCapital P234 FINISHED
Object Bonn E23133 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: Bonn | Statement: [West Germany, deFactoCapital, Bonn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bonn
Context triple: [West Germany, deFactoCapital, Bonn]
  • A. Bonn chosen
    Bonn is a historic German city on the Rhine River, best known for being the birthplace of Ludwig van Beethoven and the former seat of the federal government before reunification.
  • B. Frankfurt am Main
    Frankfurt am Main is a major German financial and transportation hub on the River Main, known for hosting the European Central Bank and one of Europe’s busiest airports.
  • C. Heidelberg
    Heidelberg is a historic university city in southwestern Germany renowned for its picturesque old town, castle ruins, and one of Europe’s oldest universities.
  • D. Osnabrück
    Osnabrück is a historic city in Lower Saxony, Germany, known for its medieval architecture and role in the Peace of Westphalia.
  • E. Hamburg
    Hamburg is Germany’s second-largest city and a major northern European port and cultural center on the River Elbe.
  • 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_69a247a8f6c08190bac804906d62ed5a completed Feb. 28, 2026, 1:40 a.m.
NER Named-entity recognition batch_69a24ae36824819080e8336a3c9f9bf8 completed Feb. 28, 2026, 1:54 a.m.
NED1 Entity disambiguation (via context triple) batch_69a2fcfeaae88190987696a6a6dafe12 completed Feb. 28, 2026, 2:34 p.m.
Created at: Feb. 28, 2026, 1:46 a.m.