Triple
T13077046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulcanian eruption |
E329604
|
entity |
| Predicate | tephraDistribution |
P46211
|
FINISHED |
| Object | proximal to 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: proximal to volcano | Statement: [Vulcanian eruption, tephraDistribution, proximal to volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tephraDistribution Context triple: [Vulcanian eruption, tephraDistribution, proximal to volcano]
-
A.
tephraVolume
Indicates the amount of volcanic tephra produced or present, typically expressed as a measurable volume.
-
B.
tephraName
Indicates that one entity is the designated name or label assigned to a specific tephra (volcanic ash or pyroclastic) unit.
-
C.
tephraFallCoverage
chosen
Indicates the spatial extent or area over which volcanic tephra (ash and debris) has been deposited or is expected to fall.
-
D.
hasPyroclasticDeposits
Indicates that an entity exhibits or contains accumulations of pyroclastic volcanic material deposited by explosive eruptions.
-
E.
volcanoDistribution
Indicates how volcanoes are spatially arranged or spread across a given area or region.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d9811828448190ac6ddd3e9c221251 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:01 p.m.