Triple
T19194777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haringvliet sluices |
E469937
|
entity |
| Predicate | KierbesluitImplementationStart |
P72290
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Haringvliet sluices, KierbesluitImplementationStart, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KierbesluitImplementationStart Context triple: [Haringvliet sluices, KierbesluitImplementationStart, 2018]
-
A.
underKierbesluit
Indicates that something falls under, is governed by, or is regulated according to a specific Kier decision or policy.
-
B.
decisionImplementedBy
Indicates that a particular decision is carried out, executed, or put into effect by a specified agent or entity.
-
C.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
D.
mandatesImplementationOf
Indicates that one entity requires or enforces the implementation or execution of another entity (such as a policy, standard, or procedure).
-
E.
implementationStart
chosen
Indicates the point in time or event at which the implementation of something (such as a plan, system, or project) begins.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a4d6b4819083fc5dd4dab05811 |
completed | April 20, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.