Triple
T35910338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santiago (city in western Guatemala) |
E1038589
|
entity |
| Predicate | nearbyVolcanicComplexType |
P109395
|
FINISHED |
| Object | lava dome complex |
—
|
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: lava dome complex | Statement: [Santiago (city in western Guatemala), nearbyVolcanicComplexType, lava dome complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyVolcanicComplexType Context triple: [Santiago (city in western Guatemala), nearbyVolcanicComplexType, lava dome complex]
-
A.
volcanoTypeNearby
chosen
Indicates that one entity is located near another entity that is classified as a particular type of volcano.
-
B.
nearVolcano
Indicates that one entity is located in close proximity to a volcano.
-
C.
volcanicProvince
Indicates a relationship where a geographic area is classified as a volcanic province, meaning it is characterized by related volcanic features or activity.
-
D.
isVolcanicEdificeOn
Indicates that a volcanic edifice is physically located on or built upon a specified surface or geological feature.
-
E.
isPartOfVolcanicSystem
Indicates that one entity belongs to, or is a component within, a larger volcanic system or complex.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: May 3, 2026, 4:07 p.m.