Triple
T823948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter III of Russia |
E17810
|
entity |
| Predicate | birthPlace |
P1
|
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: [Peter III of Russia, birthPlace, Kiel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kiel Context triple: [Peter III of Russia, birthPlace, 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.
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.
-
C.
Königsberg
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.
-
D.
Oldenburg
Oldenburg is a historic university city in northwestern Germany known for its cultural heritage and role as a regional economic center.
-
E.
Rostock
Rostock is a historic Hanseatic city in northern Germany known for its significant seaport on the Baltic Sea and its long maritime and trading tradition.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab7d3984819089aefbf12d3b3c2c |
completed | March 1, 2026, 9:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a826cf14808190a4afc2a7b6c66845 |
completed | March 4, 2026, 12:34 p.m. |
Created at: March 1, 2026, 7:38 p.m.