Triple
T2526274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guru Granth Sahib |
E56040
|
entity |
| Predicate | openingRitual |
P26551
|
FINISHED |
| Object | hukamnama (random reading) |
—
|
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: hukamnama (random reading) | Statement: [Guru Granth Sahib, openingRitual, hukamnama (random reading)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingRitual Context triple: [Guru Granth Sahib, openingRitual, hukamnama (random reading)]
-
A.
openingInvocation
Indicates the act of formally beginning an event, process, or sequence through an initiating statement, action, or call.
-
B.
appearsInRitual
Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
-
C.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
D.
ritualSpecialist
Indicates that one entity serves as a designated expert or practitioner responsible for performing or overseeing rituals in relation to another entity or context.
-
E.
partOfRitual
chosen
Indicates that an action, object, or event is included as a component or step within a larger ritual.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd255f0d081908d20cfb812c4bfc1 |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.