Triple

T5966697
Position Surface form Disambiguated ID Type / Status
Subject Battle of Königsberg E132770 entity
Predicate place P373 FINISHED
Object Königsberg E19236 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: Königsberg | Statement: [Battle of Königsberg, place, Königsberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Königsberg
Context triple: [Battle of Königsberg, place, Königsberg]
  • A. Königsberg chosen
    Königsberg was a historic Prussian city on the Baltic Sea, renowned as a major cultural and intellectual center of East Prussia and later known as Kaliningrad.
  • B. Elbing
    Elbing is a historic Baltic port city, now known as Elbląg in Poland, that played a notable role in medieval trade as part of the Hanseatic commercial network.
  • C. Potsdam
    Potsdam is a historic German city near Berlin, known for its palaces, parks, and role in major 20th-century diplomatic events.
  • D. Torgau
    Torgau is a historic town in eastern Germany, known for its Renaissance architecture and its role as a key meeting point of Allied forces near the end of World War II.
  • E. Malbork
    Malbork is a historic town in northern Poland best known for the vast medieval Malbork Castle, one of the largest brick castles in the world and a UNESCO World Heritage Site.
  • 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_69c0086c2364819091e9fe2f58fa2517 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c03a3e06848190b1d1a191db257a07 completed March 22, 2026, 6:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0e3ff62f08190be56bb9c450c9647 completed March 23, 2026, 6:55 a.m.
Created at: March 22, 2026, 4:03 p.m.