Triple
T26977534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jagannath-centric Vaishnavism |
E679498
|
entity |
| Predicate | regardsJagannathAs |
P161745
|
FINISHED |
| Object | supreme form of Krishna |
—
|
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: supreme form of Krishna | Statement: [Jagannath-centric Vaishnavism, regardsJagannathAs, supreme form of Krishna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regardsJagannathAs Context triple: [Jagannath-centric Vaishnavism, regardsJagannathAs, supreme form of Krishna]
-
A.
regardsJagannathAs
chosen
Indicates that one entity holds a particular view, attitude, or status toward Jagannath (e.g., seeing Jagannath as a deity, authority, or significant figure).
-
B.
regardsBrahmaAs
Indicates that one entity considers, views, or treats another entity as Brahma (the supreme or creator deity).
-
C.
regardsMadhvacharyaAs
Indicates that one entity holds a particular view, attitude, or evaluative stance toward Madhvacharya.
-
D.
inJainism
Indicates that the subject is associated with, belongs to, or is characterized within the religious-philosophical tradition of Jainism.
-
E.
viewOnGanesha
Indicates a perspective, opinion, or belief that an entity holds regarding Ganesha.
- 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 6:43 a.m.