Triple
T27767767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avinashi Temple |
E701649
|
entity |
| Predicate | hasDeityName |
P5606
|
FINISHED |
| Object | Avinashilingeswarar |
—
|
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: Avinashilingeswarar | Statement: [Avinashi Temple, hasDeityName, Avinashilingeswarar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeityName Context triple: [Avinashi Temple, hasDeityName, Avinashilingeswarar]
-
A.
hasDeity
chosen
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
B.
hasCultEpithetOfDeity
Indicates that a specific cult epithet or title is associated with, or used for, a particular deity.
-
C.
refersToDeityName
Indicates that one entity mentions, designates, or is associated with the name of a deity.
-
D.
hasComponentDeity
Indicates that an entity (such as a religion, mythology, or pantheon) includes a particular deity as one of its constituent or associated divine figures.
-
E.
namedAfterDeity
Indicates that one entity has been given a name derived from or in honor of a deity.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 27, 2026, 4:32 p.m.