Triple
T37259888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcanoes of Mexico |
E924230
|
entity |
| Predicate | includeVolcano |
P6356
|
FINISHED |
| Object | Popocatépetl |
E65085
|
NE 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: Popocatépetl | Statement: [Volcanoes of Mexico, includeVolcano, Popocatépetl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeVolcano Context triple: [Volcanoes of Mexico, includeVolcano, Popocatépetl]
-
A.
hasVolcano
chosen
Indicates that one entity possesses, contains, or is the location of a volcano.
-
B.
isVolcanic
Indicates that something is characterized by or related to volcanic activity, such as originating from, produced by, or associated with a volcano.
-
C.
associatedVolcano
Indicates that there is a specific volcano linked or connected to the referenced entity, such as by location, impact, or relevance.
-
D.
containsActiveVolcanoes
Indicates that the specified geographic area includes one or more volcanoes that are currently active.
-
E.
hasVolcanicLandform
Indicates that one entity possesses, contains, or is characterized by a volcanic landform (such as a volcano, caldera, or lava plateau).
- F. None of above.
Provenance (4 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4063816bd88190b3cf95b0d3d833a4 |
completed | June 27, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.