Triple
T8392120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Elgon |
E197966
|
entity |
| Predicate | calderaDescription |
P20133
|
FINISHED |
| Object | large eroded caldera |
—
|
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: large eroded caldera | Statement: [Mount Elgon, calderaDescription, large eroded caldera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calderaDescription Context triple: [Mount Elgon, calderaDescription, large eroded caldera]
-
A.
locatedInCalderaOf
Indicates that one entity is situated within the caldera (the large volcanic crater) of another entity.
-
B.
calderaDepth
Indicates the vertical distance from a caldera’s rim down to its lowest interior point.
-
C.
diameterOfCaldera
Indicates the measured width across a caldera from one rim edge to the opposite rim edge.
-
D.
isStratovolcanoOf
Indicates that a volcano is a stratovolcano specifically associated with, or located on, a particular geographic or administrative entity.
-
E.
hasSummitCaldera
chosen
Indicates that an entity (typically a volcano) possesses a caldera located at or near its summit.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb810e16b081908e2c25bfb9d590ed |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:03 p.m.