Triple
T12813928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiel Fjord |
E306341
|
entity |
| Predicate | hasHarbor |
P3007
|
FINISHED |
| Object | Kiel harbor |
E205579
|
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 harbor | Statement: [Kiel Fjord, hasHarbor, Kiel harbor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kiel harbor Context triple: [Kiel Fjord, hasHarbor, Kiel harbor]
-
A.
Kiel Naval Base
Kiel Naval Base is a major German naval installation in the Baltic port city of Kiel, historically serving as a key hub for the Imperial German Navy, the Reichsmarine, and later naval forces.
-
B.
Port of Kiel
chosen
The Port of Kiel is a major Baltic Sea seaport and ferry hub known for passenger and cargo traffic, particularly on routes between Germany and Scandinavia and the Baltic states.
-
C.
Westhafen
Westhafen is a major inland port and freight hub in Berlin, serving as one of the city’s key logistics and transportation centers.
-
D.
Schleswig harbor
Schleswig harbor is a small historic port and marina in the town of Schleswig on the Schlei inlet in northern Germany.
-
E.
Kiel Bay
Kiel Bay is a large inlet of the Baltic Sea along the coast of northern Germany, known as an important maritime area and sailing location.
- 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_69f6a544badc8190877c39728e57af6f |
completed | May 3, 2026, 1:30 a.m. |
Created at: April 9, 2026, 5:31 p.m.