Triple
T21073534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakasura |
E519170
|
entity |
| Predicate | defeatedSymbolism |
P137024
|
FINISHED |
| Object | triumph of dharma over adharma |
—
|
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: triumph of dharma over adharma | Statement: [Bakasura, defeatedSymbolism, triumph of dharma over adharma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defeatedSymbolism Context triple: [Bakasura, defeatedSymbolism, triumph of dharma over adharma]
-
A.
defeatSymbolizes
chosen
Indicates that an instance of defeat is used to symbolically represent or stand for another concept, state, or idea.
-
B.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
C.
defeat
Indicates that one entity wins against and overcomes another in a contest, conflict, or competition.
-
D.
symbolismIn
Indicates that one entity functions as a symbol or representation within the context, meaning, or interpretive framework of another entity.
-
E.
defeatedDespite
Indicates that one entity successfully defeated another entity even though circumstances or expectations suggested that defeat would be unlikely or difficult.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702d491a08190a9f5f28c0b72d38c |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:47 p.m.