Triple
T19636435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haringvliet estuary |
E471408
|
entity |
| Predicate | structureOpeningYear |
P136779
|
FINISHED |
| Object | 1970 |
—
|
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: 1970 | Statement: [Haringvliet estuary, structureOpeningYear, 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structureOpeningYear Context triple: [Haringvliet estuary, structureOpeningYear, 1970]
-
A.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
B.
originalPlannedOpeningYear
Indicates the year that was initially scheduled or intended for something to open, before any delays or changes.
-
C.
extensionOpeningYear
Indicates the year in which an extension to an existing entity (such as a building, line, or service) was officially opened or put into operation.
-
D.
approximateOpeningYear
Indicates the estimated or roughly determined year in which something (such as a facility, venue, or organization) began operating or opened.
-
E.
expansionOpeningDate
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:44 p.m.