Triple
T26499419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swaminatha Swamy Temple |
E669374
|
entity |
| Predicate | hasTitleForDeity |
P124236
|
FINISHED |
| Object | Swaminatha Swamy |
—
|
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: Swaminatha Swamy | Statement: [Swaminatha Swamy Temple, hasTitleForDeity, Swaminatha Swamy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleForDeity Context triple: [Swaminatha Swamy Temple, hasTitleForDeity, Swaminatha Swamy]
-
A.
hasShrineTitle
Indicates that an entity holds or is associated with a specific honorific or formal title used in the context of a shrine.
-
B.
templeTitleOf
Indicates that one entity is the formal religious or ceremonial title held by another entity within a temple or sacred context.
-
C.
hasCultEpithetOfDeity
chosen
Indicates that a specific cult epithet or title is associated with, or used for, a particular deity.
-
D.
refersToDeityName
Indicates that one entity mentions, designates, or is associated with the name of a deity.
-
E.
hasTitleOf
Indicates that one entity holds, bears, or is designated by the official title, name, or rank specified by another entity.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 1:11 a.m.