Triple
T555248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southwest Indian Ridge |
E11927
|
entity |
| Predicate | hasMagmatism |
P2857
|
FINISHED |
| Object | spatially variable magmatic activity |
—
|
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: spatially variable magmatic activity | Statement: [Southwest Indian Ridge, hasMagmatism, spatially variable magmatic activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagmatism Context triple: [Southwest Indian Ridge, hasMagmatism, spatially variable magmatic activity]
-
A.
hasVolcanicActivity
chosen
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
B.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
C.
volcanismType
Indicates the specific kind or style of volcanic activity or processes associated with an entity.
-
D.
hasFumaroles
Indicates the presence of fumaroles (openings emitting volcanic gases or steam) associated with an entity.
-
E.
containsVolcanicRegion
Indicates that one entity geographically includes or encompasses an area characterized by volcanic features or activity.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991dd7008190a6c1bc8bc832456d |
completed | March 1, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69a494bc1f8c8190904356f3a8e801de |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.