Triple
T19636438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haringvliet estuary |
E471408
|
entity |
| Predicate | purposeOfKierbesluit |
P128618
|
FINISHED |
| Object | restore fish migration |
—
|
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: restore fish migration | Statement: [Haringvliet estuary, purposeOfKierbesluit, restore fish migration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfKierbesluit Context triple: [Haringvliet estuary, purposeOfKierbesluit, restore fish migration]
-
A.
underKierbesluit
Indicates that something falls under, is governed by, or is regulated according to a specific Kier decision or policy.
-
B.
purposeOfGrant
Indicates that a grant is provided with the specific purpose, objective, or intended use described by the associated entity or activity.
-
C.
purposeOfLaw
chosen
Indicates that a law exists or is designed for a particular goal, function, or intended effect.
-
D.
operationalPurpose
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational context.
-
E.
knownForDecision
Indicates that an entity is recognized or notable specifically for making a particular decision.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641070528819085663c439f50148e |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.