Triple
T17089164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcán San Miguel |
E414677
|
entity |
| Predicate | hasRiskCategory |
P60801
|
FINISHED |
| Object | high-risk volcano in El Salvador |
—
|
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: high-risk volcano in El Salvador | Statement: [Volcán San Miguel, hasRiskCategory, high-risk volcano in El Salvador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiskCategory Context triple: [Volcán San Miguel, hasRiskCategory, high-risk volcano in El Salvador]
-
A.
hasHazardLevel
chosen
Indicates that an entity is associated with a specified degree or category of risk or danger.
-
B.
isThreatenedCategory
Indicates that an entity belongs to a category facing risk of harm, decline, or extinction.
-
C.
hasCountryOfRisk
Indicates that an entity is associated with a country where it faces significant exposure, vulnerability, or potential risk.
-
D.
hasSecurityCategory
Indicates that an entity is associated with a particular security classification or category defining its protection or access level.
-
E.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe9dc808190ab20537100e7ddee |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.