Triple
T34607912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izu–Tobu volcanic group |
E888643
|
entity |
| Predicate | hasDormantVolcanoes |
P6356
|
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: [Izu–Tobu volcanic group, hasDormantVolcanoes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDormantVolcanoes Context triple: [Izu–Tobu volcanic group, hasDormantVolcanoes, true]
-
A.
hasVolcanicActivity
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
chosen
Indicates that one entity possesses, contains, or is the location of a volcano.
-
C.
hasVolcanicVents
Indicates that one entity possesses or contains volcanic vents associated with another entity or location.
-
D.
hasVolcanicLandform
Indicates that one entity possesses, contains, or is characterized by a volcanic landform (such as a volcano, caldera, or lava plateau).
-
E.
hasLavaDomes
Indicates that the subject volcano possesses one or more lava domes as part of its structure or eruptive features.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 2:03 a.m.