Triple
T19857882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jayadratha |
E477181
|
entity |
| Predicate | curseRelatedToDeath |
P7531
|
FINISHED |
| Object | curse of Vriddhakshatra |
—
|
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: curse of Vriddhakshatra | Statement: [Jayadratha, curseRelatedToDeath, curse of Vriddhakshatra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curseRelatedToDeath Context triple: [Jayadratha, curseRelatedToDeath, curse of Vriddhakshatra]
-
A.
associatedCurse
chosen
Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
-
B.
curseCondition
Indicates a condition or state in which an entity is affected by a curse or cursed effect.
-
C.
hasDeathConnotation
Indicates that something is associated with, suggests, or symbolically relates to death.
-
D.
scripturalCurse
Indicates that one entity pronounces or embodies a curse upon another as recorded or prescribed in a religious or scriptural context.
-
E.
deathPractice
Indicates a relationship where an entity engages in practices, rituals, or preparations specifically related to death or dying.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6586dbbf0819089e7157d416aeaaf |
completed | April 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.