Triple
T8194187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köppen BWh |
E191385
|
entity |
| Predicate | hasSolarRadiation |
P81429
|
FINISHED |
| Object | very high |
—
|
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: very high | Statement: [Köppen BWh, hasSolarRadiation, very high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSolarRadiation Context triple: [Köppen BWh, hasSolarRadiation, very high]
-
A.
hasMaximumSolarInsolation
Indicates that an entity receives the highest level of solar radiation or sunlight intensity compared to relevant alternatives or within a given context.
-
B.
hasMinimumSolarInsolation
Indicates that an entity receives at least a specified minimum amount of solar energy (insolation) over a given area and time period.
-
C.
isSolar
Indicates that something is powered by, related to, or derived from the sun or solar energy.
-
D.
hasSolarAngle
Indicates that an entity is associated with a specific angle of incoming solar radiation relative to a reference surface or direction.
-
E.
hasMeanEarthInsolation_WPerM2
Indicates the average amount of solar power per unit area (in watts per square meter) received by Earth at the top of its atmosphere.
- F. None of above. chosen
Provenance (4 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5c1f02248190adbe56a7d6be3419 |
completed | March 31, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb46635424819085d086972b264280 |
completed | March 31, 2026, 3:58 a.m. |
Created at: March 30, 2026, 5:42 p.m.