Triple
T29571995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rendsburg ferry |
E753337
|
entity |
| Predicate | belongsToWaterwaySystem |
P2432
|
FINISHED |
| Object | Kiel Canal infrastructure |
—
|
LITERAL 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 Canal infrastructure | Statement: [Rendsburg ferry, belongsToWaterwaySystem, Kiel Canal infrastructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToWaterwaySystem Context triple: [Rendsburg ferry, belongsToWaterwaySystem, Kiel Canal infrastructure]
-
A.
isInWaterwaySystem
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
-
B.
hasWaterwayRole
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
-
C.
waterwaySystem
chosen
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
D.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
E.
hasPositionInWatercourse
Indicates that one entity occupies a specific location or position within the course of a body of water.
- 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_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 28, 2026, 5:59 p.m.