Triple
T5726882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiva Purana |
E126285
|
entity |
| Predicate | cosmologicalRoleOfShiva |
P62140
|
FINISHED |
| Object | creator |
—
|
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: creator | Statement: [Shiva Purana, cosmologicalRoleOfShiva, creator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmologicalRoleOfShiva Context triple: [Shiva Purana, cosmologicalRoleOfShiva, creator]
-
A.
cosmologicalRoleOf
chosen
Indicates the role or function an entity plays within a cosmological framework or system.
-
B.
cosmologicalRoleOfSun
Indicates the role or significance attributed to the Sun within a cosmological, mythological, or worldview framework.
-
C.
cosmologicalRealm
Indicates that one entity exists in, belongs to, or is associated with a particular cosmological realm or plane of existence relative to another.
-
D.
cosmologicalFeature
Indicates a relationship where something is identified as a large-scale structure or characteristic of the universe, such as a cosmic object, pattern, or phenomenon in cosmology.
-
E.
cosmicFunction
Indicates a relationship where an entity serves a fundamental or overarching role within a cosmic or universal system.
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c6488881909bed4a4534d57f70 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.