Triple
T5486194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swaminarayan temples |
E123586
|
entity |
| Predicate | devotionalActivity |
P21643
|
FINISHED |
| Object | kirtan singing |
—
|
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: kirtan singing | Statement: [Swaminarayan temples, devotionalActivity, kirtan singing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionalActivity Context triple: [Swaminarayan temples, devotionalActivity, kirtan singing]
-
A.
devotionalDayCommon
Indicates that two or more entities share the same religious or spiritual day of devotion or observance.
-
B.
devotionalObject
Indicates that one entity is used by or associated with another as an object of religious or spiritual devotion.
-
C.
associatedDevotion
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
D.
religiousActivity
chosen
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
-
E.
spiritualMinistry
Indicates that one entity provides religious or spiritual guidance, care, or services to another entity.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.