Triple
T18658069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dehar Power Plant |
E456117
|
entity |
| Predicate | hasSpillwayControl |
P57427
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Dehar Power Plant, hasSpillwayControl, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpillwayControl Context triple: [Dehar Power Plant, hasSpillwayControl, no]
-
A.
hasSpillway
Indicates that a dam or similar water-retaining structure is equipped with a spillway for controlled release or overflow of water.
-
B.
hasSpillwayGates
chosen
Indicates that a structure, typically a dam or spillway, is equipped with one or more controllable gates for regulating water flow.
-
C.
hasAuxiliarySpillway
Indicates that a structure, typically a dam or reservoir, is equipped with an additional spillway used to safely pass excess water beyond the capacity of the main spillway.
-
D.
hasSluicesAt
Indicates a relationship where a structure or system possesses sluice mechanisms located at a specific place or point.
-
E.
spillwayCount
Indicates the number of spillways associated with or present in a given structure or location.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55087ae8081909cb4c0ce6c809d55 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.