Triple
T19043664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurdwara Khadur Sahib |
E466072
|
entity |
| Predicate | devotionalMusic |
P134858
|
FINISHED |
| Object | Gurbani kirtan |
—
|
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: Gurbani kirtan | Statement: [Gurdwara Khadur Sahib, devotionalMusic, Gurbani kirtan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionalMusic Context triple: [Gurdwara Khadur Sahib, devotionalMusic, Gurbani kirtan]
-
A.
isDevotional
Indicates that something is intended for or characterized by religious worship, reverence, or spiritual devotion.
-
B.
devotionalPoets
Indicates a relationship in which poets are characterized by or associated with devotional (religious or spiritual) themes in their work.
-
C.
devotionalFormat
Indicates the specific structure or style in which a devotional practice, text, or activity is organized or presented.
-
D.
devotionalLanguageType
Indicates the type or category of language used in a devotional or religious context.
-
E.
devotionalSpread
Indicates the dissemination or expansion of devotional practices, beliefs, or sentiments from one source to other individuals, groups, or regions.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d802a75c8190a4ce45e5fbffc1b7 |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4c0fc3c4c8190abbfe06e1bd3325c |
completed | April 19, 2026, 11:48 a.m. |
Created at: April 10, 2026, 12:03 p.m.