Triple
T3435189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oudenhoorn |
E72433
|
entity |
| Predicate | hasDrainageSystem |
P3833
|
FINISHED |
| Object | polders and dikes |
—
|
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: polders and dikes | Statement: [Oudenhoorn, hasDrainageSystem, polders and dikes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrainageSystem Context triple: [Oudenhoorn, hasDrainageSystem, polders and dikes]
-
A.
drainageType
chosen
Indicates the kind or classification of drainage associated with or applied to an entity (e.g., how water is removed or flows from it).
-
B.
drainageStatus
Indicates the condition or effectiveness of water removal or runoff from an area, surface, or system.
-
C.
hasIrrigation
Indicates that an entity is equipped with or benefits from an irrigation system supplying water.
-
D.
isPartOfWaterSystem
Indicates that one entity is a component, segment, or subsystem within a larger water distribution, treatment, or management system.
-
E.
hasSpillway
Indicates that a dam or similar water-retaining structure is equipped with a spillway for controlled release or overflow of water.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9c3300881909f5c3544f8923b41 |
completed | March 8, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.