Triple
T20552979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varadharaja Perumal Temple |
E504643
|
entity |
| Predicate | numberInDivyaDesamList |
P46631
|
FINISHED |
| Object | one of 108 Divya Desams |
—
|
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 108 Divya Desams | Statement: [Varadharaja Perumal Temple, numberInDivyaDesamList, one of 108 Divya Desams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInDivyaDesamList Context triple: [Varadharaja Perumal Temple, numberInDivyaDesamList, one of 108 Divya Desams]
-
A.
isDivyaDesam
chosen
Indicates that a location is one of the 108 sacred Vishnu temples (Divya Desams) revered in the Tamil Vaishnavite tradition.
-
B.
hasNumberOfDivyaDesams
Indicates the specific count of Divya Desams associated with a given entity.
-
C.
rankInDivyaDesams
Indicates the relative ordering or position of an entity within the specific set or sequence of Divya Desams.
-
D.
numberInTevaramTrinity
Indicates the specific numbered position an item holds within the Tevaram Trinity sequence or set.
-
E.
positionInDasamGranth
Indicates the specific location or ordering of a referenced element within the text of the Dasam Granth.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5db052c8190801e53f6148113c8 |
completed | April 20, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.