Triple
T37391456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piraiyanivanudaya Mahadevar |
E928720
|
entity |
| Predicate | associatedTempleDeityType |
P197945
|
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: [Piraiyanivanudaya Mahadevar, associatedTempleDeityType, lingam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTempleDeityType Context triple: [Piraiyanivanudaya Mahadevar, associatedTempleDeityType, lingam]
-
A.
linkedTempleDeity
Indicates a relationship where a temple is associated with, or dedicated to, a particular deity.
-
B.
associatedWithTempleLingamType
chosen
Indicates a relationship where something is linked or connected to a specific type of temple lingam.
-
C.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
D.
associatedWithTempleName
Indicates a relationship where an entity is linked or connected to a specific temple by its name.
-
E.
closelyAssociatedDeity
Indicates a deity that is strongly connected or frequently linked to another entity, such as a person, place, object, or concept, through special association or significance.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.