Triple
T22209239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pandharpur Vitthal Temple |
E548895
|
entity |
| Predicate | languageOfDevotionalTradition |
P136332
|
FINISHED |
| Object | Marathi |
—
|
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: Marathi | Statement: [Pandharpur Vitthal Temple, languageOfDevotionalTradition, Marathi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfDevotionalTradition Context triple: [Pandharpur Vitthal Temple, languageOfDevotionalTradition, Marathi]
-
A.
languageOfScripturalTradition
Indicates the language in which a given scriptural or religious textual tradition is expressed or transmitted.
-
B.
devotionalLanguageType
Indicates the type or category of language used in a devotional or religious context.
-
C.
languageOfDevotees
chosen
Indicates the language commonly used or spoken by a group of devotees in their religious or devotional practices.
-
D.
languageOfWorship
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
E.
governingLanguageTradition
Indicates that one language tradition holds authoritative or regulatory influence over another in terms of norms, standards, or accepted 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b2aefb881909bddbabd4be0bd58 |
completed | April 28, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.