Triple
T25961661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jambukeswarar Temple |
E645553
|
entity |
| Predicate | hasPresidingLingam |
P80427
|
FINISHED |
| Object | Appu lingam |
—
|
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: Appu lingam | Statement: [Jambukeswarar Temple, hasPresidingLingam, Appu lingam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPresidingLingam Context triple: [Jambukeswarar Temple, hasPresidingLingam, Appu lingam]
-
A.
hasLinga
chosen
Indicates a relationship where an entity possesses or is associated with a linga (a symbolic representation, typically of Shiva).
-
B.
hasJyotirlingaStatus
Indicates that something holds the religious designation or status of a Jyotirlinga within the context of Hindu worship.
-
C.
hasSupremeDeityRole
Indicates that an entity holds the highest divine or ultimate god role within a religious or mythological hierarchy.
-
D.
hasDeityPosture
Indicates the specific physical stance or pose attributed to a deity in a given context.
-
E.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 22, 2026, 8:47 a.m.