Triple
T90203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atacama Desert |
E1812
|
entity |
| Predicate | hasSkyCondition |
P349
|
FINISHED |
| Object | high percentage of clear nights per year |
—
|
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 percentage of clear nights per year | Statement: [Atacama Desert, hasSkyCondition, high percentage of clear nights per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSkyCondition Context triple: [Atacama Desert, hasSkyCondition, high percentage of clear nights per year]
-
A.
hasWeather
Indicates that a location or environment is experiencing or characterized by a particular type of weather condition.
-
B.
weatherCondition
Indicates the type of atmospheric state or weather pattern (e.g., sunny, rainy, snowy) affecting a location or time period.
-
C.
skyQuality
chosen
Indicates the measured level or condition of the sky, typically in terms of clarity, brightness, or suitability for observation.
-
D.
snowCover
Indicates that one entity is covered by or blanketed with snow.
-
E.
hasClimate
Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
- 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_69a24d1a97dc819094e6c021fe9b05a7 |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24eb82d408190b0f9c786152e8e4c |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:07 a.m.