Triple

T891605
Position Surface form Disambiguated ID Type / Status
Subject Frederick I of Prussia E19250 entity
Predicate birthPlace P1 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: [Frederick I of Prussia, birthPlace, Königsberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Königsberg
Context triple: [Frederick I of Prussia, birthPlace, 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. Potsdam
    Potsdam is a historic German city near Berlin, known for its palaces, parks, and role in major 20th-century diplomatic events.
  • C. Borsigwalde
    Borsigwalde is a residential locality in the Berlin borough of Reinickendorf, known for its industrial heritage linked to the Borsig engineering works.
  • D. Kiel
    Kiel is a major port city in northern Germany on the Baltic Sea, known for its maritime industry and the annual Kiel Week sailing festival.
  • E. Cölln
    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.
  • 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_69a4939d37188190848be3d426ebc9ae completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ad019e448190ab991e85dc6d7708 completed March 1, 2026, 9:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac3b9b7eb88190b7fa4f9dbcc73d64 completed March 7, 2026, 2:52 p.m.
Created at: March 1, 2026, 7:39 p.m.