Triple
T30054580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koodal Azhagar |
E763690
|
entity |
| Predicate | isDivyaDesamDeity |
P46631
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Koodal Azhagar, isDivyaDesamDeity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDivyaDesamDeity Context triple: [Koodal Azhagar, isDivyaDesamDeity, yes]
-
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.
isKuldeviFor
Indicates a relationship where a particular goddess is revered as the ancestral or family deity (kuldevi) for a specific person, family, or lineage.
-
D.
rankInDivyaDesams
Indicates the relative ordering or position of an entity within the specific set or sequence of Divya Desams.
-
E.
deityIdentification
Indicates that one entity is identified, recognized, or designated as a deity in relation to another entity or context.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67a193c2c819087b7b55a68199771 |
completed | May 2, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:56 p.m.