Triple
T21233244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhramaramba Devi |
E523275
|
entity |
| Predicate | templeClassification |
P18959
|
FINISHED |
| Object | one of the 12 Jyotirlinga-Shakti Peetha combinations |
—
|
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: one of the 12 Jyotirlinga-Shakti Peetha combinations | Statement: [Bhramaramba Devi, templeClassification, one of the 12 Jyotirlinga-Shakti Peetha combinations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeClassification Context triple: [Bhramaramba Devi, templeClassification, one of the 12 Jyotirlinga-Shakti Peetha combinations]
-
A.
templeType
chosen
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
B.
religiousSiteType
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
C.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
-
D.
templeNumberWorldwide
Indicates the total count of temples that exist worldwide.
-
E.
shrineType
Indicates the specific category or kind of shrine associated with an 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734b1524c8190a77eaf2fabd601c3 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:45 p.m.