Triple
T518307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Mexican Volcanic Belt |
E10756
|
entity |
| Predicate | hasVolcanoStatus |
P8376
|
FINISHED |
| Object | active volcanoes |
—
|
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: active volcanoes | Statement: [Trans-Mexican Volcanic Belt, hasVolcanoStatus, active volcanoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolcanoStatus Context triple: [Trans-Mexican Volcanic Belt, hasVolcanoStatus, active volcanoes]
-
A.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
B.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
C.
volcanicStatus
chosen
Indicates the current activity state or condition of a volcano, such as active, dormant, or extinct.
-
D.
containsVolcanicRegion
Indicates that one entity geographically includes or encompasses an area characterized by volcanic features or activity.
-
E.
hasFumaroles
Indicates the presence of fumaroles (openings emitting volcanic gases or steam) associated with an 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f19ee6748190916603ef3a9e27f3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.