Triple
T3788559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Gorges Dam |
E89587
|
entity |
| Predicate | reservoirNormalElevation |
P47800
|
FINISHED |
| Object | 175 m above sea level |
—
|
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: 175 m above sea level | Statement: [Three Gorges Dam, reservoirNormalElevation, 175 m above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservoirNormalElevation Context triple: [Three Gorges Dam, reservoirNormalElevation, 175 m above sea level]
-
A.
reservoirElevation
chosen
Indicates the height or level of water stored in a reservoir relative to a defined reference point.
-
B.
reservoirLiveStorageCapacity_m3
Indicates the volume of water that a reservoir can actively store and use, measured in cubic meters.
-
C.
elevationAboveLake
Indicates the vertical height or altitude of something relative to the surface level of a specified lake.
-
D.
damHeight
Indicates the vertical height of a dam structure, typically measured from its base or foundation to its crest.
-
E.
waterLevelRise
Indicates that the level of water in a given area or container has increased over time.
- 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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecefa3608190a7a20ed6df6a64b2 |
completed | March 9, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69aee743c8d08190a9f9c97b836bd703 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:14 p.m.