Triple
T18782717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europoortkering |
E459297
|
entity |
| Predicate | engineeringProjectType |
P39623
|
FINISHED |
| Object | large-scale hydraulic engineering project |
—
|
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: large-scale hydraulic engineering project | Statement: [Europoortkering, engineeringProjectType, large-scale hydraulic engineering project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineeringProjectType Context triple: [Europoortkering, engineeringProjectType, large-scale hydraulic engineering project]
-
A.
typeOfProject
chosen
Indicates the specific category or kind of project that an entity is associated with or classified under.
-
B.
typeOfEngineering
Indicates that one entity is a specific branch, category, or kind of engineering to which the other entity belongs.
-
C.
productionProject
Indicates that an entity is involved in or associated with a specific production project, typically as part of its creation, development, or execution.
-
D.
developmentProject
Indicates a relationship where an organized effort or initiative is undertaken to plan, create, improve, or expand something over a defined period.
-
E.
shipProject
Indicates initiating, managing, or executing the delivery and release of a project from development to completion or deployment.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5977d7c5c8190ab2aadb47283965d |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.