Triple
T19812270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halahala poison |
E475974
|
entity |
| Predicate | triggeredAction |
P134741
|
FINISHED |
| Object | gods seeking refuge in Shiva |
—
|
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: gods seeking refuge in Shiva | Statement: [Halahala poison, triggeredAction, gods seeking refuge in Shiva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggeredAction Context triple: [Halahala poison, triggeredAction, gods seeking refuge in Shiva]
-
A.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
B.
triggeredResponse
Indicates that one entity’s action or event causes another entity to produce a specific reaction or output.
-
C.
promptedAction
chosen
Indicates that one entity initiates or triggers another entity to perform a specific action.
-
D.
triggeredFrom
Indicates that one event, action, or process was initiated or caused as a result of another specific event, action, or process.
-
E.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6542c9c5c81908772e88caa067e63 |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.