Triple
T22402632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Meredith |
E553796
|
entity |
| Predicate | elevationAtFullPool |
P47800
|
FINISHED |
| Object | about 2,965 feet 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: about 2,965 feet above sea level | Statement: [Lake Meredith, elevationAtFullPool, about 2,965 feet above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationAtFullPool Context triple: [Lake Meredith, elevationAtFullPool, about 2,965 feet above sea level]
-
A.
elevationAtBase
Indicates the height or altitude measured at the base or lowest point of an object or feature relative to a reference level.
-
B.
reservoirElevation
chosen
Indicates the height or level of water stored in a reservoir relative to a defined reference point.
-
C.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
D.
elevationFeetApproximate
Indicates the approximate elevation of an entity above sea level, measured in feet.
-
E.
hasFloorElevation
Indicates that one entity has a specified vertical height or level above a reference point (such as sea level or ground) for its floor.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b565c48190b0f6c19f17995b40 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.