Triple
T38335818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacaya |
E1037952
|
entity |
| Predicate | hasCalderaComplex |
P127517
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Pacaya, hasCalderaComplex, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCalderaComplex Context triple: [Pacaya, hasCalderaComplex, yes]
-
A.
isCaldera
Indicates that something is a volcanic caldera, i.e., a large basin-like depression formed by the collapse of land following a volcanic eruption.
-
B.
isCalderaOf
Indicates that one geological depression or basin is the caldera formed by the volcanic activity of another volcanic structure or system.
-
C.
containsCaldera
chosen
Indicates that one geological feature, typically a volcano or volcanic region, has a caldera located within its bounds.
-
D.
hasCalderaType
Indicates that a caldera is classified as being of a particular type based on its formation or characteristics.
-
E.
calderaSystem
Indicates a geological relationship where a volcanic system is associated with, contained within, or characterized by a caldera structure.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0061454944819088a0babfe60f69fc |
completed | May 10, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_6a0060b9ee108190b91e8d99a16f2b30 |
completed | May 10, 2026, 10:40 a.m. |
Created at: May 3, 2026, 4:30 p.m.