Triple
T20777220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dismemberment of Sati’s body |
E511383
|
entity |
| Predicate | purposeInMyth |
P36122
|
FINISHED |
| Object | to restore cosmic balance |
—
|
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: to restore cosmic balance | Statement: [Dismemberment of Sati’s body, purposeInMyth, to restore cosmic balance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeInMyth Context triple: [Dismemberment of Sati’s body, purposeInMyth, to restore cosmic balance]
-
A.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
B.
designedPurposeInFiction
Indicates that something is intentionally created within a fictional context to serve a particular role, function, or narrative purpose.
-
C.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
D.
moralOfMyth
Indicates the underlying lesson, ethical teaching, or message conveyed by a myth.
-
E.
ritualPurpose
chosen
Indicates the intended function, goal, or role that a ritual is meant to serve or fulfill.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26bbe108190bb7c3e5b416e44fe |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.