Triple
T6418503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Erebus |
E127886
|
entity |
| Predicate | isWorldExtreme |
P46620
|
FINISHED |
| Object | southernmost active volcano |
—
|
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: southernmost active volcano | Statement: [Mount Erebus, isWorldExtreme, southernmost active volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWorldExtreme Context triple: [Mount Erebus, isWorldExtreme, southernmost active volcano]
-
A.
geographicalExtreme
chosen
Indicates that one place represents an extreme (such as the northernmost, highest, deepest, etc.) within a specified geographic or administrative area.
-
B.
hasExtremeWeatherCharacteristic
Indicates that something possesses a notable or defining feature related to extreme weather conditions.
-
C.
worldType
Indicates the classification or category of world or environment that an entity is associated with.
-
D.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
-
E.
hasClimate
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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068eb6c988190b54de6182d0f490d |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:42 p.m.