Triple
T17943378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakutia Airlines |
E448639
|
entity |
| Predicate | operatesInClimate |
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: [Yakutia Airlines, operatesInClimate, subarctic climate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInClimate Context triple: [Yakutia Airlines, operatesInClimate, subarctic climate]
-
A.
designedForClimate
Indicates that something has been intentionally created or adapted to function optimally under specific climate or environmental conditions.
-
B.
operatingTemperatureCategory
Indicates the temperature range classification within which an entity is designed or expected to operate.
-
C.
operatingCondition
Indicates the specific state, requirements, or circumstances under which an entity functions or is intended to be used.
-
D.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad97611c8190a861467ae51f6c48 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.