Triple
T33085823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maithon Dam |
E846635
|
entity |
| Predicate | spillwayFunction |
P175791
|
FINISHED |
| Object | flood discharge |
—
|
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: flood discharge | Statement: [Maithon Dam, spillwayFunction, flood discharge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spillwayFunction Context triple: [Maithon Dam, spillwayFunction, flood discharge]
-
A.
hasSpillway
Indicates that a dam or similar water-retaining structure is equipped with a spillway for controlled release or overflow of water.
-
B.
spillwayLocation
Indicates the location where a spillway is situated relative to another referenced feature or area.
-
C.
spillwayCount
Indicates the number of spillways associated with or present in a given structure or location.
-
D.
typeOfSpillway
Indicates the specific kind or design category of a spillway associated with a structure or location.
-
E.
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.
- F. None of above. chosen
Provenance (4 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:26 a.m.