Triple
T19595382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putrakameshti sacrifice of Dasharatha |
E470334
|
entity |
| Predicate | linkedRitualType |
P42159
|
FINISHED |
| Object | Putrakameshti yajna |
—
|
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: Putrakameshti yajna | Statement: [Putrakameshti sacrifice of Dasharatha, linkedRitualType, Putrakameshti yajna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedRitualType Context triple: [Putrakameshti sacrifice of Dasharatha, linkedRitualType, Putrakameshti yajna]
-
A.
relatedRitual
Indicates that one entity is associated with, connected to, or involved in the performance or context of a particular ritual.
-
B.
hasRitualType
chosen
Indicates that an entity is associated with, or classified by, a particular type or category of ritual.
-
C.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
D.
appearsInRitual
Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
-
E.
hasRitualRule
Indicates that an entity is governed by, or associated with, a specific ritual rule or prescribed ceremonial guideline.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407a09608190aa1df92f8c21f9e7 |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.