Triple
T26903960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jambukeswarar Temple |
E678101
|
entity |
| Predicate | consortDeityForm |
P46302
|
FINISHED |
| Object | Parvati as Akhilandeswari |
—
|
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: Parvati as Akhilandeswari | Statement: [Jambukeswarar Temple, consortDeityForm, Parvati as Akhilandeswari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consortDeityForm Context triple: [Jambukeswarar Temple, consortDeityForm, Parvati as Akhilandeswari]
-
A.
hasConsortDeityForm
chosen
Indicates that an entity has a consort specifically in their deity or divine form.
-
B.
hasConsortDeity
Indicates that one deity is the consort (spouse or intimate divine partner) of another deity.
-
C.
mainDeityForm
Indicates that one entity is the primary or canonical divine form or manifestation of another deity.
-
D.
spiritualConsortOf
Indicates a relationship in which one entity is regarded as the spiritual or sacred partner, counterpart, or consort of another.
-
E.
deifiedFormOf
Indicates that one entity is the deified or god-like form or manifestation of 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fb229a48190920ee562a6084c36 |
completed | May 2, 2026, 4 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:52 a.m.