Triple
T27569716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | southern flank of Cho Oyu |
E695998
|
entity |
| Predicate | hasClimaticZone |
P193
|
FINISHED |
| Object | high alpine |
—
|
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 alpine | Statement: [southern flank of Cho Oyu, hasClimaticZone, high alpine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimaticZone Context triple: [southern flank of Cho Oyu, hasClimaticZone, high alpine]
-
A.
shareClimateZones
Indicates that two entities are located in regions classified under the same climate zone or zones.
-
B.
hasClimate
chosen
Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
-
C.
climatologicalRegion
Indicates that one entity is a climatological region associated with, or characterizing the climate of, another entity.
-
D.
hasClimateContext
Indicates that something is associated with, influenced by, or relevant to climate-related conditions, factors, or considerations.
-
E.
climateZonesShowcased
Indicates that certain climate zones are being presented or highlighted, typically for display, comparison, or informational purposes.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 1:42 p.m.