Triple
T1848613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antarctic Circle |
E41341
|
entity |
| Predicate | climaticZone |
P193
|
FINISHED |
| Object | polar climate zone |
—
|
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: polar climate zone | Statement: [Antarctic Circle, climaticZone, polar climate zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climaticZone Context triple: [Antarctic Circle, climaticZone, polar climate zone]
-
A.
climatologicalType
Indicates the classification of a climate or weather pattern that characterizes a place, period, or condition.
-
B.
isEcologicalZone
Indicates that one entity functions as, or is classified as, an ecological zone in relation to another entity.
-
C.
hasClimate
chosen
Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
-
D.
hasClimateContext
Indicates that something is associated with, influenced by, or relevant to climate-related conditions, factors, or considerations.
-
E.
ecoregion
Indicates that one entity is located within, associated with, or belongs to the same ecological region as another entity.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdca6d8819083c66f3a29fd9fd1 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.