Triple
T28513452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Observatoire Volcanologique de Goma |
E721551
|
entity |
| Predicate | riskTypeMonitored |
P39679
|
FINISHED |
| Object | lava flows |
—
|
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: lava flows | Statement: [Observatoire Volcanologique de Goma, riskTypeMonitored, lava flows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskTypeMonitored Context triple: [Observatoire Volcanologique de Goma, riskTypeMonitored, lava flows]
-
A.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
B.
riskTypesManaged
Indicates that one entity is responsible for handling, controlling, or overseeing specific categories of risk associated with another entity or context.
-
C.
riskElement
Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
-
D.
threatTypeMonitored
chosen
Indicates that a particular type of threat is being actively observed, tracked, or watched for by some monitoring process or system.
-
E.
riskBased
Indicates that something is determined, prioritized, or managed according to the level or assessment of risk involved.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f77c86c8190bb05cffae7c17a00 |
completed | May 2, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:14 a.m.