Triple
T2649710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ubinas volcano |
E53866
|
entity |
| Predicate | eruptiveHistory |
P34963
|
FINISHED |
| Object | historical eruptions recorded since at least the 16th century |
—
|
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: historical eruptions recorded since at least the 16th century | Statement: [Ubinas volcano, eruptiveHistory, historical eruptions recorded since at least the 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptiveHistory Context triple: [Ubinas volcano, eruptiveHistory, historical eruptions recorded since at least the 16th century]
-
A.
eruptionFrequency
Indicates how often an eruption event occurs within a given time period.
-
B.
eruptionVEI
Indicates the Volcanic Explosivity Index (VEI) assigned to a particular volcanic eruption event.
-
C.
notableEruptionAge
chosen
Indicates the age or time period at which a notable volcanic eruption associated with an entity occurred.
-
D.
eruptionHeight
Indicates the vertical distance or altitude reached by an eruption from its source.
-
E.
lastEruption
Indicates the time or event corresponding to the most recent eruption associated with a given 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd91ca1288190ba302b04bac4c153 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.