Triple
T38550448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meera Temple |
E925094
|
entity |
| Predicate | worshipLanguageTradition |
P3115
|
FINISHED |
| Object | Rajasthani bhajans of Meerabai |
—
|
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: Rajasthani bhajans of Meerabai | Statement: [Meera Temple, worshipLanguageTradition, Rajasthani bhajans of Meerabai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipLanguageTradition Context triple: [Meera Temple, worshipLanguageTradition, Rajasthani bhajans of Meerabai]
-
A.
worshipTradition
Indicates that one entity follows, practices, or is associated with a particular religious or spiritual worship tradition.
-
B.
languageOfWorship
chosen
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
C.
languageOfGospelTraditionally
Indicates the language in which a particular Gospel is traditionally believed or held to have been written or transmitted.
-
D.
worshipStyle
Indicates the manner or form in which worship or religious devotion is practiced or expressed.
-
E.
liturgicalTradition
Indicates the specific religious rite or ceremonial tradition according to which a worship service, practice, or community operates.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd3163d0881909d3209cd7cb81c10 |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.