Triple
T7911851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annamalaiyar Temple |
E183717
|
entity |
| Predicate | presidingFormOfShiva |
P7648
|
FINISHED |
| Object | lingam |
—
|
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: lingam | Statement: [Annamalaiyar Temple, presidingFormOfShiva, lingam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presidingFormOfShiva Context triple: [Annamalaiyar Temple, presidingFormOfShiva, lingam]
-
A.
VajranabhaIs
Indicates that something or someone is identified as or characterized by being Vajranabha.
-
B.
isDivyaDesam
Indicates that a location is one of the 108 sacred Vishnu temples (Divya Desams) revered in the Tamil Vaishnavite tradition.
-
C.
mainDeity
chosen
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
D.
hasConsortDeityForm
Indicates that an entity has a consort specifically in their deity or divine form.
-
E.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a725b8c8190a530adb3107a95dd |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:04 p.m.