Triple
T20965286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | पाण्डु |
E516349
|
entity |
| Predicate | मृत्यु का कारण (परंपरागत कथा) |
P100625
|
FINISHED |
| Object | शाप भंग करने पर मृत्यु |
—
|
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: शाप भंग करने पर मृत्यु | Statement: [पाण्डु, मृत्यु का कारण (परंपरागत कथा), शाप भंग करने पर मृत्यु]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: मृत्यु का कारण (परंपरागत कथा) Context triple: [पाण्डु, मृत्यु का कारण (परंपरागत कथा), शाप भंग करने पर मृत्यु]
-
A.
traditionalMannerOfDeath
Indicates that an entity died in a way that follows or reflects a culturally recognized or customary method of death.
-
B.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
C.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
D.
legendaryCauseOfDeath
chosen
Indicates a legendary or mythic account of how an entity died, as opposed to a historically verified cause of death.
-
E.
traditionallyDied
Indicates that an entity died in the manner, context, or circumstances specified by a particular tradition or customary account.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb72ef4c8190bebdd2cef3c2148c |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:32 p.m.