Triple

T12813907
Position Surface form Disambiguated ID Type / Status
Subject Kiel Fjord E306341 entity
Predicate adjacentCity P5707 FINISHED
Object Kiel E108871 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: Kiel | Statement: [Kiel Fjord, adjacentCity, Kiel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kiel
Context triple: [Kiel Fjord, adjacentCity, Kiel]
  • A. Kiel chosen
    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.
  • B. Kiel-Holtenau
    Kiel-Holtenau is a district of the German city of Kiel, known for its location at the Baltic Sea entrance of the Kiel Canal and its historic canal locks and lighthouse.
  • C. Frombork
    Frombork is a historic town in northern Poland best known as the place where astronomer Nicolaus Copernicus lived, worked, and was buried, and for its prominent cathedral complex overlooking the Vistula Lagoon.
  • D. Itzehoe
    Itzehoe is a historic town in northern Germany known for its medieval origins and role as a regional center in the state of Schleswig-Holstein.
  • E. Gdańsk
    Gdańsk is a major Polish port city on the Baltic Sea, known for its rich Hanseatic history, shipyards, and role in the origins of the Solidarity movement.
  • 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_69d7bdf46c448190b1faa55aaacb6317 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96e9adcf08190a12801adcc613477 completed April 10, 2026, 9:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69f69b97ffd481909c540f52c781f63f completed May 3, 2026, 12:49 a.m.
Created at: April 9, 2026, 5:31 p.m.