Triple
T16443842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuego Volcano |
E399373
|
entity |
| Predicate | activityFrequency |
P122812
|
FINISHED |
| Object | near-continuous low-level activity |
—
|
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: near-continuous low-level activity | Statement: [Fuego Volcano, activityFrequency, near-continuous low-level activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activityFrequency Context triple: [Fuego Volcano, activityFrequency, near-continuous low-level activity]
-
A.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
B.
humanActivityLevel
Indicates the degree or intensity of activity or movement performed by a human over a given period or in a given context.
-
C.
currentActivityLevel
Indicates the present intensity or degree of activity that an entity is engaged in at a given moment.
-
D.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
E.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
- F. None of above. chosen
Provenance (4 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cd9d474819091b4a80de1019c54 |
completed | April 18, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.