Triple
T20352967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gandhari |
E496063
|
entity |
| Predicate | curseContent |
P7531
|
FINISHED |
| Object | destruction of Yadava clan |
—
|
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: destruction of Yadava clan | Statement: [Gandhari, curseContent, destruction of Yadava clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curseContent Context triple: [Gandhari, curseContent, destruction of Yadava clan]
-
A.
curseCondition
Indicates a condition or state in which an entity is affected by a curse or cursed effect.
-
B.
associatedCurse
chosen
Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
-
C.
scripturalCurse
Indicates that one entity pronounces or embodies a curse upon another as recorded or prescribed in a religious or scriptural context.
-
D.
reasonForCurse
Indicates the cause, justification, or triggering event that led to a curse being placed on someone or something.
-
E.
timeOfCurse
Indicates the specific time at which a curse is cast, activated, or takes effect in relation to an entity or event.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67851c7088190ba960a33c6dfa824 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.