Triple
T24279126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gangaikonda Cholapuram |
E605489
|
entity |
| Predicate | mainDeityOfPrincipalTemple |
P7648
|
FINISHED |
| Object | Shiva |
—
|
NE NERFINISHED |
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: Shiva | Statement: [Gangaikonda Cholapuram, mainDeityOfPrincipalTemple, Shiva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDeityOfPrincipalTemple Context triple: [Gangaikonda Cholapuram, mainDeityOfPrincipalTemple, Shiva]
-
A.
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).
-
B.
patronDeityOf
Indicates that one entity serves as the protective or primary deity associated with, worshipped by, or presiding over another entity (such as a person, group, or place).
-
C.
mainDeityLocation
Indicates the place or setting where the primary deity associated with something is located or worshipped.
-
D.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
E.
relatedDeityResidence
Indicates that a deity is associated with, dwells in, or is traditionally believed to reside in a particular place or realm.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5032f48190a027e2d8b382ee79 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.