Triple
T26691433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makuti |
E672893
|
entity |
| Predicate | elevationRelativeToZambeziValley |
P137035
|
FINISHED |
| Object | higher elevation escarpment |
—
|
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: higher elevation escarpment | Statement: [Makuti, elevationRelativeToZambeziValley, higher elevation escarpment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationRelativeToZambeziValley Context triple: [Makuti, elevationRelativeToZambeziValley, higher elevation escarpment]
-
A.
elevationAboveLake
Indicates the vertical height or altitude of something relative to the surface level of a specified lake.
-
B.
elevationAboveSurroundingPlains
Indicates that something is situated at a higher altitude than the nearby flat or low-lying surrounding plains.
-
C.
hasElevationRelativeToSeaLevel
Indicates the elevation or height of an entity measured relative to mean sea level.
-
D.
elevationAboveWater
Indicates the vertical distance by which one entity is positioned above the surface level of a body of water.
-
E.
hasTypicalElevationRelativeTo
chosen
Indicates the usual height or altitude of one entity in comparison to a referenced baseline or other entity.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 3:26 a.m.