Triple
T1270953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maeslantkering |
E15706
|
entity |
| Predicate | designedReturnPeriod |
P28063
|
FINISHED |
| Object | 1 in 10,000 years storm surge |
—
|
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: 1 in 10,000 years storm surge | Statement: [Maeslantkering, designedReturnPeriod, 1 in 10,000 years storm surge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedReturnPeriod Context triple: [Maeslantkering, designedReturnPeriod, 1 in 10,000 years storm surge]
-
A.
hasDesignPeriod
Indicates that something was created, planned, or developed during a specified historical or stylistic design period.
-
B.
designPeriod
Indicates the time span during which something is planned, designed, or conceptually developed before implementation or production.
-
C.
timePeriodProposed
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
-
D.
designLifetime
Indicates the intended duration or operational period for which something is designed to function as specified.
-
E.
designedToAvoid
Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
- 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_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. |
| PDg | Predicate description generation | batch_69a4bfa205ec81909d8170b398345615 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:50 p.m.