Triple
T4710608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zandkreekdam |
E104499
|
entity |
| Predicate | hasEngineeringRole |
P15961
|
FINISHED |
| Object | storm surge barrier element |
—
|
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: storm surge barrier element | Statement: [Zandkreekdam, hasEngineeringRole, storm surge barrier element]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEngineeringRole Context triple: [Zandkreekdam, hasEngineeringRole, storm surge barrier element]
-
A.
hasEngineeringBy
Indicates that something is designed, planned, or constructed by a specified engineer or engineering entity.
-
B.
hasEngineeringSignificance
chosen
Indicates that something holds notable importance, impact, or relevance within an engineering context or for engineering activities.
-
C.
hasProductionRole
Indicates that an entity holds a specific role or function in the production or creation process of another entity.
-
D.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
-
E.
hasEngineeringStyle
Indicates that an entity possesses or exhibits a particular engineering approach, methodology, or design style in how it is created, structured, or operates.
- 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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:17 p.m.