Triple
T7409797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1971 Teneguía eruption |
E170970
|
entity |
| Predicate | explosivity |
P76611
|
FINISHED |
| Object | relatively mild |
—
|
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: relatively mild | Statement: [1971 Teneguía eruption, explosivity, relatively mild]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explosivity Context triple: [1971 Teneguía eruption, explosivity, relatively mild]
-
A.
explosiveClass
Indicates the classification or category assigned to an explosive based on its type, properties, or regulatory class.
-
B.
explosiveMaterialUsed
Indicates that an explosive material was employed or involved in carrying out a particular action or event.
-
C.
explosiveDevice
Indicates the presence or involvement of an object designed to explode or cause an explosion in relation to the associated entities.
-
D.
numberOfExplosions
Indicates the count of distinct explosion events associated with an entity or situation.
-
E.
explosiveFillerMass
Indicates the amount of explosive material contained within an object or device.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f29d77848190a6170eb25483224f |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f15c36d48190bc75353d3f67555a |
completed | March 27, 2026, 9:06 p.m. |
Created at: March 27, 2026, 3:10 p.m.