Triple
T18613474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bend Glacier |
E454957
|
entity |
| Predicate | associatedVolcanoStatus |
P8376
|
FINISHED |
| Object | extinct 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: extinct volcano | Statement: [Bend Glacier, associatedVolcanoStatus, extinct volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedVolcanoStatus Context triple: [Bend Glacier, associatedVolcanoStatus, extinct volcano]
-
A.
associatedVolcano
Indicates that there is a specific volcano linked or connected to the referenced entity, such as by location, impact, or relevance.
-
B.
volcanicStatus
chosen
Indicates the current activity state or condition of a volcano, such as active, dormant, or extinct.
-
C.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
D.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
E.
discoveredAsVolcano
Indicates that an entity was identified, recognized, or confirmed to be a volcano.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d030d488190a992d10d3d28b4ad |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.