Triple
T28361733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köppen climate classification |
E718378
|
entity |
| Predicate | definesCategoryCAs |
P34022
|
FINISHED |
| Object | temperate climates |
—
|
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: temperate climates | Statement: [Köppen climate classification, definesCategoryCAs, temperate climates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesCategoryCAs Context triple: [Köppen climate classification, definesCategoryCAs, temperate climates]
-
A.
categoryDefinedIn
Indicates that a category is formally specified or established within a particular source, context, or definitional framework.
-
B.
categoryDefinedBy
Indicates that a category is established, characterized, or delimited according to a specific defining criterion, rule, or source.
-
C.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
D.
definesClassification
chosen
Indicates that one entity specifies or establishes the classification or category to which another entity belongs.
-
E.
designatorCategory
Indicates the classification or type assigned to a designator within a given system or context.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 28, 2026, 12:52 a.m.