Triple
T14170828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colla people |
E351201
|
entity |
| Predicate | altitudeOfHomeland |
P21269
|
FINISHED |
| Object | high-altitude plateau |
—
|
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: high-altitude plateau | Statement: [Colla people, altitudeOfHomeland, high-altitude plateau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altitudeOfHomeland Context triple: [Colla people, altitudeOfHomeland, high-altitude plateau]
-
A.
hasHighestPointAboveSeaLevel
Indicates that the highest point of one entity is located at a greater elevation above sea level than that of another entity.
-
B.
countryAltitudeCharacteristic
Indicates a characteristic relationship specifying the typical or notable altitude or elevation associated with a country.
-
C.
locatedAtAltitude
chosen
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
D.
countryOfHighestPoint
Indicates the country within whose territory a given location’s highest elevation point is found.
-
E.
highestElevationApprox
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b472288190b4a271daa54aa6cd |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:01 a.m.