Triple
T6805222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekarma Volcano |
E156286
|
entity |
| Predicate | hasPyroclasticDeposits |
P73104
|
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: [Ekarma Volcano, hasPyroclasticDeposits, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPyroclasticDeposits Context triple: [Ekarma Volcano, hasPyroclasticDeposits, true]
-
A.
hasVolcanicAsh
Indicates that there is volcanic ash present on, in, or associated with a specified entity or location.
-
B.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
C.
hasLavaDomes
Indicates that the subject volcano possesses one or more lava domes as part of its structure or eruptive features.
-
D.
isVolcanic
Indicates that something is characterized by or related to volcanic activity, such as originating from, produced by, or associated with a volcano.
-
E.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
- F. None of above. chosen
Provenance (4 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2ea459c819095388218d53c250a |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d2a8f9188190abbb8c730e7b5edf |
completed | March 27, 2026, 6:55 p.m. |
Created at: March 27, 2026, 2:16 p.m.