Triple
T26789290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Plata (Huila) |
E670468
|
entity |
| Predicate | hasVolcanoAccess |
P167301
|
FINISHED |
| Object | Nevado del Huila |
—
|
NE NERFINISHED |
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: Nevado del Huila | Statement: [La Plata (Huila), hasVolcanoAccess, Nevado del Huila]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolcanoAccess Context triple: [La Plata (Huila), hasVolcanoAccess, Nevado del Huila]
-
A.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
B.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
C.
hasVolcanicVents
Indicates that one entity possesses or contains volcanic vents associated with another entity or location.
-
D.
hasVolcanoObservatory
Indicates that a place or region possesses an established volcano observatory facility that monitors volcanic activity there.
-
E.
isOnVolcanicIsland
Indicates that one entity is located on, or geographically situated upon, an island formed by volcanic activity.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 27, 2026, 4:15 a.m.