Triple
T38299695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanjangud Srikanteshwara Temple |
E1032187
|
entity |
| Predicate | subShrineDeity |
P190618
|
FINISHED |
| Object | Parvati |
—
|
NE NERFINISHED |
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: Parvati | Statement: [Nanjangud Srikanteshwara Temple, subShrineDeity, Parvati]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subShrineDeity Context triple: [Nanjangud Srikanteshwara Temple, subShrineDeity, Parvati]
-
A.
subsidiaryShrineOf
Indicates that one shrine functions as a secondary or dependent shrine that is formally associated with and subordinate to another main shrine.
-
B.
shrineType
Indicates the specific category or kind of shrine associated with an entity.
-
C.
servedDeity
Indicates that one entity acted in service, devotion, or worship toward a particular deity.
-
D.
stateShrineOf
Indicates that one entity is officially designated as a state-recognized shrine associated with or located within another entity (typically a state or region).
-
E.
recognizedAsShrineBy
Indicates that something is regarded or designated as a shrine by a particular person, group, or authority.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:30 p.m.