Triple
T30854587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köppen Cfa |
E785883
|
entity |
| Predicate | hasClimaticZoneType |
P193
|
FINISHED |
| Object | mesothermal climate |
—
|
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: mesothermal climate | Statement: [Köppen Cfa, hasClimaticZoneType, mesothermal climate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimaticZoneType Context triple: [Köppen Cfa, hasClimaticZoneType, mesothermal climate]
-
A.
majorClimaticZone
Indicates that one entity is classified as belonging to a particular major climatic zone defined by broad, long-term climate characteristics.
-
B.
shareClimateZones
Indicates that two entities are located in regions classified under the same climate zone or zones.
-
C.
agroClimateZone
Indicates the specific agricultural climate zone in which an area or activity is situated or classified.
-
D.
climatologicalRegion
Indicates that one entity is a climatological region associated with, or characterizing the climate of, another entity.
-
E.
hasClimate
chosen
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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 29, 2026, 8:46 p.m.