Triple
T17284554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selva Alta |
E419616
|
entity |
| Predicate | climaticFeature |
P193
|
FINISHED |
| Object | frequent cloud cover |
—
|
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: frequent cloud cover | Statement: [Selva Alta, climaticFeature, frequent cloud cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climaticFeature Context triple: [Selva Alta, climaticFeature, frequent cloud cover]
-
A.
climatologicalType
Indicates the classification of a climate or weather pattern that characterizes a place, period, or condition.
-
B.
climatologicalSignificance
Indicates the degree to which something is important, influential, or relevant within the context of climate or long-term weather patterns.
-
C.
hasClimate
chosen
Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
-
D.
hasExtremeWeatherCharacteristic
Indicates that something possesses a notable or defining feature related to extreme weather conditions.
-
E.
climaticRole
Indicates the role or influence that something has on climate patterns 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4332bd324819080795152293d6d43 |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:40 a.m.