Triple
T38043045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurdwara Rakab Ganj Sahib |
E949540
|
entity |
| Predicate | hasKirtan |
P39850
|
FINISHED |
| Object | daily recitation of Gurbani |
—
|
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: daily recitation of Gurbani | Statement: [Gurdwara Rakab Ganj Sahib, hasKirtan, daily recitation of Gurbani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKirtan Context triple: [Gurdwara Rakab Ganj Sahib, hasKirtan, daily recitation of Gurbani]
-
A.
hasRaga
Indicates that something (such as a musical piece, performance, or composition) is associated with or based on a specific raga.
-
B.
hasGandharam
Indicates a relationship where one entity possesses, is associated with, or includes a gandharam (a specific musical note or tonal element) in relation to another entity.
-
C.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
-
D.
hasKaraokeVersion
Indicates that an entity has a corresponding karaoke (instrumental or sing-along) version of itself.
-
E.
hasRitualMusic
chosen
Indicates that one entity is associated with or characterized by ritual music used in formal or ceremonial practices.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.