Triple
T3116953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Popocatépetl |
E65085
|
entity |
| Predicate | hasLavaComposition |
P15890
|
FINISHED |
| Object | andesitic |
—
|
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: andesitic | Statement: [Popocatépetl, hasLavaComposition, andesitic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLavaComposition Context triple: [Popocatépetl, hasLavaComposition, andesitic]
-
A.
hasLavaFlow
Indicates that one entity exhibits, contains, or is associated with a flow of lava originating from volcanic activity.
-
B.
isStratovolcanoComposedOf
Indicates that a stratovolcano is made up of, or constructed from, a particular material or set of materials.
-
C.
hasMineral
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
D.
hasSurfaceComposition
Indicates that one entity has a surface made up of, or characterized by, the material or composition specified by another entity.
-
E.
typicalLavaType
chosen
Indicates the usual or characteristic type of lava associated with a given volcanic feature, eruption, or context.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada4e5d1488190a2ab199625fdf05d |
completed | March 8, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.