Triple
T26799727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhuvaneshvari Upanishad |
E671064
|
entity |
| Predicate | describesDeityAs |
P57193
|
FINISHED |
| Object | supreme cosmic power |
—
|
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 cosmic power | Statement: [Bhuvaneshvari Upanishad, describesDeityAs, supreme cosmic power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesDeityAs Context triple: [Bhuvaneshvari Upanishad, describesDeityAs, supreme cosmic power]
-
A.
roleOfReferencedDeity
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
B.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
C.
attributeOfDeity
chosen
Indicates that something is a characteristic, quality, or property belonging to a deity.
-
D.
portraysDeity
Indicates that one entity represents, depicts, or characterizes another entity as a deity or divine being.
-
E.
depictedDeity
Indicates that one entity is a deity who is shown or represented in an image, artwork, or visual depiction associated with 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 4:22 a.m.