Triple
T3454018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sardar Sarovar Dam |
E72857
|
entity |
| Predicate | spillwayCapacity_m3_per_s |
P5503
|
FINISHED |
| Object | 85000 |
—
|
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: 85000 | Statement: [Sardar Sarovar Dam, spillwayCapacity_m3_per_s, 85000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spillwayCapacity_m3_per_s Context triple: [Sardar Sarovar Dam, spillwayCapacity_m3_per_s, 85000]
-
A.
hasSpillway
Indicates that a dam or similar water-retaining structure is equipped with a spillway for controlled release or overflow of water.
-
B.
waterFlowRate
chosen
Indicates the rate at which water moves or is transported through a given point or system over time.
-
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.
reservoirTotalCapacity
Indicates the maximum volume of water that a reservoir is designed to hold when full.
-
E.
inflowWatercourse
Indicates that one watercourse flows into or feeds another water body or watercourse.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbaa457fc8190824ca00254e962f9 |
completed | March 8, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.