Triple

T3552306
Position Surface form Disambiguated ID Type / Status
Subject Battle of Breslau (1757) E75137 entity
Predicate cityCaptured P8502 FINISHED
Object Breslau E238097 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: Breslau | Statement: [Battle of Breslau (1757), cityCaptured, Breslau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Breslau
Context triple: [Battle of Breslau (1757), cityCaptured, Breslau]
  • A. Breslau chosen
    Breslau is the historical German name for the city now known as Wrocław in southwestern Poland, a major cultural and academic center in Central Europe.
  • B. Stettin
    Stettin, now known as Szczecin, is a major port city on the Oder River in northwestern Poland near the Baltic Sea.
  • C. Oppeln
    Oppeln is the historical German name for the city of Opole, a major cultural and administrative center in southwestern Poland’s Silesia region.
  • D. Frankfurt (Oder)
    Frankfurt (Oder) is a German city on the Oder River at the Polish border, known as a historic university and trade center in the state of Brandenburg.
  • E. Cieszyn
    Cieszyn is a historic town in southern Poland on the Olza River, known for its shared Polish-Czech heritage and well-preserved old town.
  • 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_69ad85d33c6c819081d5ac1df13b5680 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc05256f081908b8d6a5df917e679 completed March 8, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69b402dfb0688190a65b41c8dc13ee97 completed March 13, 2026, 12:28 p.m.
Created at: March 8, 2026, 3:20 p.m.