Triple
T6298712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolberg |
E141196
|
entity |
| Predicate | hasGermanName |
P1435
|
FINISHED |
| Object | Kolberg |
E141196
|
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: Kolberg | Statement: [Kolberg, hasGermanName, Kolberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kolberg Context triple: [Kolberg, hasGermanName, Kolberg]
-
A.
Kolberg
chosen
Kolberg is a historic Baltic Sea port city in present-day Kołobrzeg, Poland, known for its strategic military importance and spa tourism.
-
B.
Marienwerder
Marienwerder is a historic town in former West Prussia, now known as Kwidzyn in Poland, noted for its medieval architecture and Teutonic Order castle.
-
C.
Danzig harbor
Danzig harbor was the port area of the Free City of Danzig (now Gdańsk, Poland) that played a pivotal role at the outbreak of World War II, notably as the site of the German attack on Westerplatte.
-
D.
Schwarmstedt
Schwarmstedt is a municipality in Lower Saxony, Germany, situated in the Heidekreis district along the River Aller.
-
E.
Löwenberg
Löwenberg is a town in Germany known for its cultural and municipal partnership as a twin town of Weilburg.
- 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_69c008cf0ad4819095def81e2bd42f9f |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0643ddaa48190b3ea8061fc1d9dc4 |
completed | March 22, 2026, 9:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c51993b8ec8190a0813d66851ac201 |
completed | March 26, 2026, 11:33 a.m. |
Created at: March 22, 2026, 4:27 p.m.