Triple
T17219762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dionisio Pulido |
E417943
|
entity |
| Predicate | knownEvent |
P93648
|
FINISHED |
| Object | eruption of Parícutin volcano in 1943 |
—
|
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: eruption of Parícutin volcano in 1943 | Statement: [Dionisio Pulido, knownEvent, eruption of Parícutin volcano in 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownEvent Context triple: [Dionisio Pulido, knownEvent, eruption of Parícutin volcano in 1943]
-
A.
significantEventInvolves
chosen
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
B.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
C.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
D.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
E.
introducedEvent
Indicates that an entity is responsible for bringing an event into existence or initiating it for the first time.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42ddc3cb88190a67e35164d710d9d |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.