Triple
T8816294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haarlemmermeer drainage project |
E209784
|
entity |
| Predicate | appliesEngineeringDiscipline |
P77595
|
FINISHED |
| Object | hydraulic engineering |
—
|
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: hydraulic engineering | Statement: [Haarlemmermeer drainage project, appliesEngineeringDiscipline, hydraulic engineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesEngineeringDiscipline Context triple: [Haarlemmermeer drainage project, appliesEngineeringDiscipline, hydraulic engineering]
-
A.
hasEngineeringBy
Indicates that something is designed, planned, or constructed by a specified engineer or engineering entity.
-
B.
typeOfEngineering
chosen
Indicates that one entity is a specific branch, category, or kind of engineering to which the other entity belongs.
-
C.
engineeringEmphasis
Indicates that something places a primary focus or specialization on engineering principles, methods, or activities.
-
D.
designDiscipline
Indicates a relationship where an entity is associated with, categorized under, or practices a particular field or branch of design.
-
E.
hasEngineeringSignificance
Indicates that something holds notable importance, impact, or relevance within an engineering context or for engineering activities.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc600bd8a88190ad891a96201d796b |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.