Triple
T19949968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parashara |
E479527
|
entity |
| Predicate | cosmicRoleInTexts |
P137962
|
FINISHED |
| Object | narrator of Vishnu Purana |
—
|
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: narrator of Vishnu Purana | Statement: [Parashara, cosmicRoleInTexts, narrator of Vishnu Purana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicRoleInTexts Context triple: [Parashara, cosmicRoleInTexts, narrator of Vishnu Purana]
-
A.
cosmologicalRoleOf
Indicates the role or function an entity plays within a cosmological framework or system.
-
B.
cosmicFunction
Indicates a relationship where an entity serves a fundamental or overarching role within a cosmic or universal system.
-
C.
cosmicSymbolism
Indicates a relationship where one entity symbolically represents or embodies cosmic, universal, or celestial principles in relation to another.
-
D.
cosmicAssociation
Indicates a relationship in which entities are linked, connected, or correlated through cosmic or celestial factors, influences, or contexts.
-
E.
cosmicDimension
Indicates a relationship where something exists, operates, or is characterized within a particular cosmic or universal scale, realm, or dimension.
- F. None of above. chosen
Provenance (4 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6a93548190875af2176e6901a7 |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.