Triple
T30273401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aryaghat cremation site |
E769865
|
entity |
| Predicate | typeOfRitePerformed |
P3305
|
FINISHED |
| Object | antyeshti (last rites) |
—
|
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: antyeshti (last rites) | Statement: [Aryaghat cremation site, typeOfRitePerformed, antyeshti (last rites)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRitePerformed Context triple: [Aryaghat cremation site, typeOfRitePerformed, antyeshti (last rites)]
-
A.
ordinationRite
Indicates the formal religious ceremony or ritual through which a person is conferred an office or ordained to a specific role.
-
B.
observedInRite
Indicates that an entity participates in or is witnessed as part of a specific ritual or ceremonial practice.
-
C.
ceremonyTypeOfficiated
Indicates the specific type of ceremony that an officiant conducted or presided over.
-
D.
ceremonyType
chosen
Indicates the specific kind or category of ceremony associated with an event or relationship.
-
E.
ritualEvent
Indicates that an event is a ritual or ceremonial occurrence, typically involving prescribed actions, symbols, or practices performed according to tradition or custom.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
Created at: April 29, 2026, 7:44 p.m.