Triple
T4822995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maeslantkering |
E107753
|
entity |
| Predicate | spanWhenClosed |
P59865
|
FINISHED |
| Object | about 360 metres |
—
|
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: about 360 metres | Statement: [Maeslantkering, spanWhenClosed, about 360 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spanWhenClosed Context triple: [Maeslantkering, spanWhenClosed, about 360 metres]
-
A.
closureFrequency
Indicates how often a particular process, event, or entity is closed or brought to an end within a given period.
-
B.
closedDuring
Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
-
C.
closingContains
Indicates that one closing element, event, or period fully includes another within its temporal or structural bounds.
-
D.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
E.
closedBy
Indicates that one entity performs the action of closing, finishing, or terminating another entity (such as a task, issue, or process).
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6dda5e808190a26ec85e4499d8e4 |
completed | March 20, 2026, 3:55 p.m. |
Created at: March 20, 2026, 1:24 p.m.