Triple
T890653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haringvlietdam |
E19229
|
entity |
| Predicate | hasNavigationFunction |
P14917
|
FINISHED |
| Object | allows ship passage via locks |
—
|
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: allows ship passage via locks | Statement: [Haringvlietdam, hasNavigationFunction, allows ship passage via locks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationFunction Context triple: [Haringvlietdam, hasNavigationFunction, allows ship passage via locks]
-
A.
hasNavigationUse
chosen
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
B.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
-
C.
hasTransportFunction
Indicates that an entity serves to move or carry something (such as people, goods, or signals) from one place or state to another.
-
D.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
E.
enablesNavigationBetween
Indicates that one entity provides the means or capability for moving or transitioning between two other entities or locations.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad0086a081908c47c285896a1f3c |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9372e88190b5a9db4afdc045c6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.