Triple
T27697345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundareswarar shrine |
E698333
|
entity |
| Predicate | consortShrineOf |
P86928
|
FINISHED |
| Object | Meenakshi shrine |
—
|
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: Meenakshi shrine | Statement: [Sundareswarar shrine, consortShrineOf, Meenakshi shrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consortShrineOf Context triple: [Sundareswarar shrine, consortShrineOf, Meenakshi shrine]
-
A.
hasConsortDeity
Indicates that one deity is the consort (spouse or intimate divine partner) of another deity.
-
B.
associatedShrine
Indicates that there is a specific shrine linked or connected to the given entity, typically as its dedicated or related place of worship or reverence.
-
C.
guardianShrineOf
Indicates a relationship where one entity serves as a protective or custodial shrine dedicated to another entity.
-
D.
spiritualConsortOf
chosen
Indicates a relationship in which one entity is regarded as the spiritual or sacred partner, counterpart, or consort of another.
-
E.
associatedShrineComplex
Indicates that one entity is linked or connected to a particular shrine complex, typically through location, function, or religious association.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635a0a2788190bc17046fa79d26a6 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:55 p.m.