Triple
T34111625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guru Nanak Gurpurab |
E874851
|
entity |
| Predicate | devotionalMusicForm |
P129877
|
FINISHED |
| Object | Shabad Kirtan |
—
|
NE NERFINISHED |
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: Shabad Kirtan | Statement: [Guru Nanak Gurpurab, devotionalMusicForm, Shabad Kirtan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionalMusicForm Context triple: [Guru Nanak Gurpurab, devotionalMusicForm, Shabad Kirtan]
-
A.
devotionalMusic
Indicates a relationship where music is created, performed, or used as an expression of religious or spiritual devotion toward a deity, faith, or sacred context.
-
B.
hasDevotionalForm
chosen
Indicates that one entity takes or possesses a devotional expression, format, or mode in relation to another entity or context.
-
C.
devotionalFormat
Indicates the specific structure or style in which a devotional practice, text, or activity is organized or presented.
-
D.
isDevotional
Indicates that something is intended for or characterized by religious worship, reverence, or spiritual devotion.
-
E.
devotionalElement
Indicates a relationship where something serves as or functions as an element used in devotional or religious practice.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70cb544848190aaeb8f766a95aaff |
completed | May 3, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:53 a.m.