Triple
T26799761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhuvaneshvari Upanishad |
E671064
|
entity |
| Predicate | cosmicRoleOfDeity |
P137962
|
FINISHED |
| Object | dissolver of worlds |
—
|
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: dissolver of worlds | Statement: [Bhuvaneshvari Upanishad, cosmicRoleOfDeity, dissolver of worlds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicRoleOfDeity Context triple: [Bhuvaneshvari Upanishad, cosmicRoleOfDeity, dissolver of worlds]
-
A.
cosmologyDeity
Indicates that a deity is associated with, governs, or is central to a particular cosmological system or view of the universe.
-
B.
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.
-
C.
cosmicRoleInTexts
chosen
Indicates the role or function an entity is described as having within cosmic or mythological contexts in texts.
-
D.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
E.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
- 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_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 4:22 a.m.