Triple
T14098494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parthasarathy shrine |
E339317
|
entity |
| Predicate | principalDeityRole |
P85058
|
FINISHED |
| Object | charioteer of Arjuna |
—
|
LITERAL FINISHED |
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: charioteer of Arjuna | Statement: [Parthasarathy shrine, principalDeityRole, charioteer of Arjuna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalDeityRole Context triple: [Parthasarathy shrine, principalDeityRole, charioteer of Arjuna]
-
A.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
B.
hasSupremeDeityRole
Indicates that an entity holds the highest divine or ultimate god role within a religious or mythological hierarchy.
-
C.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
D.
mainDeityForm
Indicates that one entity is the primary or canonical divine form or manifestation of another deity.
-
E.
deityCategory
chosen
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fb926288190a7f0f50d1d585d76 |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.