Triple
T4145481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concepción Volcano |
E89370
|
entity |
| Predicate | riskToPopulation |
P17586
|
FINISHED |
| Object | significant |
—
|
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: significant | Statement: [Concepción Volcano, riskToPopulation, significant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskToPopulation Context triple: [Concepción Volcano, riskToPopulation, significant]
-
A.
riskGroup
Indicates that an entity belongs to a category of individuals or items that share an elevated level of risk relative to others.
-
B.
targetedPopulation
chosen
Indicates the group of individuals or entities that an action, intervention, or effect is specifically directed toward.
-
C.
riskModel
Indicates a relationship where an entity serves as or is associated with a model used to assess, quantify, or manage risk for another entity or situation.
-
D.
riskBasis
Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
-
E.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.