Triple
T28513413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Observatoire Volcanologique de Goma |
E721551
|
entity |
| Predicate | regionMonitored |
P90127
|
FINISHED |
| Object | Virunga volcanic region |
—
|
NE NERFINISHED |
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: Virunga volcanic region | Statement: [Observatoire Volcanologique de Goma, regionMonitored, Virunga volcanic region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionMonitored Context triple: [Observatoire Volcanologique de Goma, regionMonitored, Virunga volcanic region]
-
A.
observesRegion
chosen
Indicates that an entity monitors, watches, or collects information about a specific geographic or spatial region.
-
B.
regionAnalyzed
Indicates that a specific geographic or spatial region has been examined or evaluated, typically to extract information, detect patterns, or assess certain properties.
-
C.
borderMonitored
Indicates that a border between two regions or entities is actively being watched, controlled, or surveilled.
-
D.
surveillanceArea
Indicates the area or region that is monitored or observed by a surveillance system or agent.
-
E.
monitoringBoundaryFor
Indicates that one entity serves as the defined limit or scope within which another entity’s monitoring or surveillance activities are applied.
- 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_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 28, 2026, 3:14 a.m.