Triple
T5583046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narasimha |
E146684
|
entity |
| Predicate | killingMethod |
P2115
|
FINISHED |
| Object | tore open Hiranyakashipu with claws |
—
|
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: tore open Hiranyakashipu with claws | Statement: [Narasimha, killingMethod, tore open Hiranyakashipu with claws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killingMethod Context triple: [Narasimha, killingMethod, tore open Hiranyakashipu with claws]
-
A.
usedMethodOfKilling
chosen
Indicates that one entity employed a particular method or means to carry out a killing of another entity.
-
B.
deathMethod
Indicates the specific way or means by which a death occurred.
-
C.
finalSinkingMethod
Indicates the method or process ultimately used to sink or deliberately submerge an object, typically a vessel or structure.
-
D.
killedBy
Indicates that one entity caused the death of another entity.
-
E.
typeOfKilling
Indicates a specific manner, method, or category of killing that characterizes how the killing was carried out.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0208333f08190bf0049b6bdd280f5 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.