Triple
T7123811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Ranganathaswamy Temple, Srirangam |
E166009
|
entity |
| Predicate | rankInDivyaDesams |
P74991
|
FINISHED |
| Object | first among 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: first among 108 Divya Desams | Statement: [Sri Ranganathaswamy Temple, Srirangam, rankInDivyaDesams, first among 108 Divya Desams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInDivyaDesams Context triple: [Sri Ranganathaswamy Temple, Srirangam, rankInDivyaDesams, first among 108 Divya Desams]
-
A.
hasNumberOfDivyaDesams
Indicates the specific count of Divya Desams associated with a given entity.
-
B.
isDivyaDesam
Indicates that a location is one of the 108 sacred Vishnu temples (Divya Desams) revered in the Tamil Vaishnavite tradition.
-
C.
positionInVeda
Indicates the specific location or ordering of a referenced element within the structure of a Vedic text.
-
D.
numberInTevaramTrinity
Indicates the specific numbered position an item holds within the Tevaram Trinity sequence or set.
-
E.
dashavataraPosition
Indicates the specific ordinal position an incarnation holds within the traditional sequence of the ten principal avatars (Dashavatara).
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e64ab1f881908bc2468cc72d2544 |
completed | March 27, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:44 p.m.