Triple

T1985995
Position Surface form Disambiguated ID Type / Status
Subject Hanseatic League E43142 entity
Predicate hasMember P10 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: [Hanseatic League, hasMember, Königsberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Königsberg
Context triple: [Hanseatic League, hasMember, 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. 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.
  • D. 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.
  • E. Borsigwalde
    Borsigwalde is a residential locality in the Berlin borough of Reinickendorf, known for its industrial heritage linked to the Borsig engineering works.
  • 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_69a88713ddc88190a969715658ebe7a8 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb8232d788190938f261fd4b2f2fd completed March 7, 2026, 5:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae0331eec881909463163fb71e4eba completed March 8, 2026, 11:16 p.m.
Created at: March 4, 2026, 7:37 p.m.