Triple
T38335796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacaya |
E1037952
|
entity |
| Predicate | hasLavaFountains |
P201730
|
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, hasLavaFountains, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLavaFountains Context triple: [Pacaya, hasLavaFountains, yes]
-
A.
hasLavaFlow
Indicates that one entity exhibits, contains, or is associated with a flow of lava originating from volcanic activity.
-
B.
hasFumaroles
Indicates the presence of fumaroles (openings emitting volcanic gases or steam) associated with an entity.
-
C.
hasVolcanicLake
Indicates that an entity contains or features a lake formed in or directly associated with volcanic activity.
-
D.
hasLavaDomes
Indicates that the subject volcano possesses one or more lava domes as part of its structure or eruptive features.
-
E.
hasVolcanicVents
Indicates that one entity possesses or contains volcanic vents associated with another entity or location.
- F. None of above. chosen
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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_6a0018cebf688190bbd90ac79d250182 |
completed | May 10, 2026, 5:34 a.m. |
Created at: May 3, 2026, 4:30 p.m.