Triple
T9731224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bely Island |
E235745
|
entity |
| Predicate | hasHarshClimate |
P17982
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bely Island, hasHarshClimate, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarshClimate Context triple: [Bely Island, hasHarshClimate, true]
-
A.
hasExtremeWeatherCharacteristic
chosen
Indicates that something possesses a notable or defining feature related to extreme weather conditions.
-
B.
hasClimate
Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
-
C.
hasClimateContext
Indicates that something is associated with, influenced by, or relevant to climate-related conditions, factors, or considerations.
-
D.
nativeToClimate
Indicates that an entity naturally originates from or is originally adapted to a specified climate or climatic region.
-
E.
climaticChallenge
Indicates a relationship where an entity faces, contributes to, or is affected by significant difficulties or stresses arising from climate or weather 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eb2373c81909139c7a2ff2aa541 |
completed | April 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:21 p.m.