Triple
T37290653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Hunza |
E925656
|
entity |
| Predicate | typicalVillageElevation |
P1977
|
FINISHED |
| Object | around 2500 to 3000 metres |
—
|
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: around 2500 to 3000 metres | Statement: [Upper Hunza, typicalVillageElevation, around 2500 to 3000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVillageElevation Context triple: [Upper Hunza, typicalVillageElevation, around 2500 to 3000 metres]
-
A.
typicalElevationRange
chosen
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
B.
hasTypicalElevationRelativeTo
Indicates the usual height or altitude of one entity in comparison to a referenced baseline or other entity.
-
C.
elevationAboveTown
Indicates that one location is situated at a higher elevation relative to a specified town.
-
D.
hasAverageElevation
Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
-
E.
typicalCamp2Elevation
Indicates the usual or characteristic elevation at which a particular camp (such as a base or staging camp) is located.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.