Triple
T18450912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drupada |
E450778
|
entity |
| Predicate | performedYajnaFor |
P131674
|
FINISHED |
| Object | getting a son to kill Drona |
—
|
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: getting a son to kill Drona | Statement: [Drupada, performedYajnaFor, getting a son to kill Drona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedYajnaFor Context triple: [Drupada, performedYajnaFor, getting a son to kill Drona]
-
A.
performedSupplication
Indicates that one entity directed a humble, earnest request or prayer (a supplication) toward another entity.
-
B.
hasAltarDedication
Indicates that an altar is dedicated to, in honor of, or in association with a particular entity or purpose.
-
C.
prayedDuring
Indicates that one entity performed prayer at some time within the duration of another specified event or time interval.
-
D.
hasLifecycleRitual
Indicates that an entity is associated with a ritual or ceremonial practice marking a significant stage or transition in its lifecycle.
-
E.
hasVotiveOfferings
Indicates that an entity possesses or is associated with votive offerings dedicated or presented in a religious or ritual context.
- F. None of above. chosen
Provenance (4 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52648476c8190a5d8c3297d836f62 |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:31 a.m.