Triple
T32392855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galeras Volcano |
E827721
|
entity |
| Predicate | hasHighRisk |
P150896
|
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: [Galeras Volcano, hasHighRisk, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighRisk Context triple: [Galeras Volcano, hasHighRisk, true]
-
A.
hasRiskFor
Indicates that one entity is susceptible or exposed to the possibility of experiencing a harmful event, condition, or outcome associated with another entity.
-
B.
hasRiskStatus
chosen
Indicates the level or category of risk currently associated with an entity.
-
C.
hasRiskFrom
Indicates that one entity is exposed to or may suffer potential harm, loss, or adverse effects as a result of another entity.
-
D.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
E.
riskIfTooHigh
Indicates that a certain level or value becomes risky or dangerous when it exceeds a specified threshold.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: May 1, 2026, 12:52 a.m.