Triple
T1270957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maeslantkering |
E15706
|
entity |
| Predicate | testClosureFrequency |
P16914
|
FINISHED |
| Object | once per year |
—
|
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: once per year | Statement: [Maeslantkering, testClosureFrequency, once per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testClosureFrequency Context triple: [Maeslantkering, testClosureFrequency, once per year]
-
A.
closureContext
Indicates the surrounding scope or environment in which an operation, expression, or function is defined and executed, capturing the variables and bindings available to it.
-
B.
numberOfExecutions
Indicates the count of times a particular action, process, or event has been carried out.
-
C.
performedFrequency
chosen
Indicates how often an action or activity is carried out within a given time period.
-
D.
timingMethod
Indicates the method or technique used to measure or record the timing of an event or process.
-
E.
closureProcess
Indicates the procedure or set of actions carried out to formally conclude, finalize, or terminate an ongoing activity, case, or process.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c06ae7b88190a1e0b5232d84a7b1 |
completed | March 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.