Triple
T4925195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garibaldi Volcanic Belt |
E110559
|
entity |
| Predicate | volcanoMorphology |
P17518
|
FINISHED |
| Object | stratovolcanoes |
—
|
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: stratovolcanoes | Statement: [Garibaldi Volcanic Belt, volcanoMorphology, stratovolcanoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volcanoMorphology Context triple: [Garibaldi Volcanic Belt, volcanoMorphology, stratovolcanoes]
-
A.
typeOfVolcanicFeature
chosen
Indicates that one entity is classified as a specific kind or category of volcanic feature represented by the other entity.
-
B.
volcanismType
Indicates the specific kind or style of volcanic activity or processes associated with an entity.
-
C.
volcanicOrigin
Indicates that something originates from, is produced by, or is directly associated with volcanic activity or processes.
-
D.
volcanicProvince
Indicates a relationship where a geographic area is classified as a volcanic province, meaning it is characterized by related volcanic features or activity.
-
E.
islandFormingVolcano
Indicates a volcano whose eruptive activity creates or has created an island above the surrounding water.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7033c430819088e62f14979aa83c |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.