Triple
T32911266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jogulamba Temple |
E841882
|
entity |
| Predicate | stateShaktiPeethaOf |
P92828
|
FINISHED |
| Object | Telangana |
—
|
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: Telangana | Statement: [Jogulamba Temple, stateShaktiPeethaOf, Telangana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateShaktiPeethaOf Context triple: [Jogulamba Temple, stateShaktiPeethaOf, Telangana]
-
A.
shaktiPeethaStatus
Indicates the status or classification of a site with respect to being recognized as a Shakti Peetha.
-
B.
shaktiPeethaBodyPart
Indicates a relationship where a Shakti Peetha is associated with a specific body part of the goddess Sati that is believed to have fallen at that sacred site.
-
C.
hasNumberOfDivyaDesams
Indicates the specific count of Divya Desams associated with a given entity.
-
D.
hasAshramaAt
Indicates that an ashrama (hermitage or spiritual retreat) is located at or associated with a specific place.
-
E.
stateShrineOf
chosen
Indicates that one entity is officially designated as a state-recognized shrine associated with or located within another entity (typically a state or region).
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: May 1, 2026, 1:19 a.m.