Triple
T32602245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danjiangkou Dam |
E833405
|
entity |
| Predicate | elevationOfReservoirNormal |
P47800
|
FINISHED |
| Object | 170 m |
—
|
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: 170 m | Statement: [Danjiangkou Dam, elevationOfReservoirNormal, 170 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationOfReservoirNormal Context triple: [Danjiangkou Dam, elevationOfReservoirNormal, 170 m]
-
A.
reservoirElevation
chosen
Indicates the height or level of water stored in a reservoir relative to a defined reference point.
-
B.
hasNormalWaterLevel
Indicates that an entity’s water level is within the expected or standard range, neither abnormally high nor low.
-
C.
associatedWithReservoirElevationFluctuation
Indicates a relationship in which something is linked to, influenced by, or involved in changes in the water level of a reservoir over time.
-
D.
reservoir
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
E.
reservoirLiveStorageCapacity_m3
Indicates the volume of water that a reservoir can actively store and use, measured in cubic meters.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: May 1, 2026, 1:05 a.m.