Triple
T13377586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pico de Orizaba region |
E319228
|
entity |
| Predicate | mainVolcanoType |
P41618
|
FINISHED |
| Object | stratovolcano (Pico de Orizaba) |
—
|
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: stratovolcano (Pico de Orizaba) | Statement: [Pico de Orizaba region, mainVolcanoType, stratovolcano (Pico de Orizaba)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainVolcanoType Context triple: [Pico de Orizaba region, mainVolcanoType, stratovolcano (Pico de Orizaba)]
-
A.
volcanismType
Indicates the specific kind or style of volcanic activity or processes associated with an entity.
-
B.
typeOfVolcanicFeature
Indicates that one entity is classified as a specific kind or category of volcanic feature represented by the other entity.
-
C.
isVolcanic
Indicates that something is characterized by or related to volcanic activity, such as originating from, produced by, or associated with a volcano.
-
D.
volcanoTypeNearby
Indicates that one entity is located near another entity that is classified as a particular type of volcano.
-
E.
containsVolcanoType
chosen
Indicates that a geographic area or feature includes at least one volcano of the specified type.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce3fec48190a5443d87c85477a3 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.