Triple
T4710609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zandkreekdam |
E104499
|
entity |
| Predicate | isPartOfHydraulicSystem |
P36984
|
FINISHED |
| Object | Delta Works hydraulic infrastructure |
—
|
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: Delta Works hydraulic infrastructure | Statement: [Zandkreekdam, isPartOfHydraulicSystem, Delta Works hydraulic infrastructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfHydraulicSystem Context triple: [Zandkreekdam, isPartOfHydraulicSystem, Delta Works hydraulic infrastructure]
-
A.
isPartOfWaterSystem
chosen
Indicates that one entity is a component, segment, or subsystem within a larger water distribution, treatment, or management system.
-
B.
partOfSystem
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
C.
isPartOfAviationSystem
Indicates that something functions as a component or subsystem within a broader aviation system or infrastructure.
-
D.
usesWorkingFluid
Indicates that one entity operates or functions by employing another entity as its working fluid.
-
E.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
- 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.