Triple
T34607212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sluis Gaarkeuken |
E888625
|
entity |
| Predicate | waterwayInfrastructureType |
P136606
|
FINISHED |
| Object | lock |
—
|
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: lock | Statement: [sluis Gaarkeuken, waterwayInfrastructureType, lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwayInfrastructureType Context triple: [sluis Gaarkeuken, waterwayInfrastructureType, lock]
-
A.
isInlandWaterwayInfrastructure
chosen
Indicates that something is part of the physical facilities or structures used for inland waterway transport, such as canals, locks, or related navigational infrastructure.
-
B.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
C.
constructedWaterway
Indicates a water channel or route that has been artificially created or significantly modified by human construction.
-
D.
waterwayFunction
Indicates the primary role or purpose that a waterway serves, such as transportation, irrigation, drainage, or recreation.
-
E.
maritimeInfrastructureType
Indicates the specific kind of maritime infrastructure associated with or characterizing an entity (e.g., port, harbor, dock, or related facility).
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 1, 2026, 2:03 a.m.