Triple
T35997240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Vicente Pacaya |
E1041020
|
entity |
| Predicate | hasVolcanicTourism |
P185707
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [San Vicente Pacaya, hasVolcanicTourism, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolcanicTourism Context triple: [San Vicente Pacaya, hasVolcanicTourism, true]
-
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.
hasIslandTourism
Indicates that an entity engages in or supports tourism activities specifically related to islands.
-
D.
hasVolcanicLandform
Indicates that one entity possesses, contains, or is characterized by a volcanic landform (such as a volcano, caldera, or lava plateau).
-
E.
volcanoAttractionStatus
Indicates the relationship between a volcano and its current attraction status, such as whether it is open, closed, restricted, or otherwise available for visitation.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4:07 p.m.