Triple
T14466387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CA-YT |
E358719
|
entity |
| Predicate | associatedClimate |
P193
|
FINISHED |
| Object | subarctic 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: subarctic climate | Statement: [CA-YT, associatedClimate, subarctic climate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedClimate Context triple: [CA-YT, associatedClimate, subarctic climate]
-
A.
hasClimate
chosen
Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
-
B.
climateBetween
Indicates that something (such as a location, period, or condition) has a climate that lies within a specified range or intermediate state between two other climatic conditions.
-
C.
climateDependent
Indicates that the existence, behavior, or outcome of something is determined or significantly influenced by climatic conditions.
-
D.
climateSubgroup
Indicates that one climate category is a more specific subgroup or subtype within another, broader climate category.
-
E.
hasClimateContext
Indicates that something is associated with, influenced by, or relevant to climate-related conditions, factors, or considerations.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91f6d4c08190a12e9a5901ee3508 |
completed | April 14, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.