Triple
T35292241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiles volcano |
E1019258
|
entity |
| Predicate | hasVolcanicEdificeComposition |
P118514
|
FINISHED |
| Object | lava flows |
—
|
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: lava flows | Statement: [Chiles volcano, hasVolcanicEdificeComposition, lava flows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolcanicEdificeComposition Context triple: [Chiles volcano, hasVolcanicEdificeComposition, lava flows]
-
A.
volcanoComposition
chosen
Indicates that a volcano is composed of, or primarily made up of, a specified material or set of materials.
-
B.
isStratovolcanoComposedOf
Indicates that a stratovolcano is made up of, or constructed from, a particular material or set of materials.
-
C.
hasVolcanicLandform
Indicates that one entity possesses, contains, or is characterized by a volcanic landform (such as a volcano, caldera, or lava plateau).
-
D.
isVolcanicEdificeOn
Indicates that a volcanic edifice is physically located on or built upon a specified surface or geological feature.
-
E.
hasVolcanicProduct
Indicates that an entity possesses, contains, or is associated with material or products originating from volcanic activity.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.