Triple
T29571818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiel-Holtenau |
E753333
|
entity |
| Predicate | waterwayEntranceOf |
P31589
|
FINISHED |
| Object | Nord-Ostsee-Kanal zur Ostsee |
—
|
NE NERFINISHED |
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: Nord-Ostsee-Kanal zur Ostsee | Statement: [Kiel-Holtenau, waterwayEntranceOf, Nord-Ostsee-Kanal zur Ostsee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwayEntranceOf Context triple: [Kiel-Holtenau, waterwayEntranceOf, Nord-Ostsee-Kanal zur Ostsee]
-
A.
waterwayAccess
chosen
Indicates that one location has direct access to a waterway (such as a river, canal, or sea route) that can be used for transport, navigation, or related activities.
-
B.
waterwayThrough
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
-
C.
waterwayDestination
Indicates that a waterway leads to, flows into, or terminates at a specified destination.
-
D.
partOfWaterway
Indicates that one water-related feature is a constituent or segment of a larger waterway system.
-
E.
waterwayJunction
Indicates a point where two or more waterways meet, intersect, or branch from one another.
- F. None of above.
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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 28, 2026, 5:59 p.m.