Triple
T890648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haringvlietdam |
E19229
|
entity |
| Predicate | KierbesluitImplementation |
P9960
|
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: [Haringvlietdam, KierbesluitImplementation, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KierbesluitImplementation Context triple: [Haringvlietdam, KierbesluitImplementation, 2018]
-
A.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
B.
makesDecisionBy
Indicates that one entity determines or chooses an outcome, course of action, or judgment by means of another entity, method, or process.
-
C.
decisionBody
chosen
Indicates that one entity serves as the authoritative body or group responsible for making a particular decision regarding another entity or matter.
-
D.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
E.
mandatesImplementationOf
Indicates that one entity requires or enforces the implementation or execution of another entity (such as a policy, standard, or procedure).
- 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.