Triple
T20080987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RajasuyaYajna |
E499998
|
entity |
| Predicate | consequenceInEpic |
P40708
|
FINISHED |
| Object | tension leading to dice game |
—
|
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: tension leading to dice game | Statement: [RajasuyaYajna, consequenceInEpic, tension leading to dice game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceInEpic Context triple: [RajasuyaYajna, consequenceInEpic, tension leading to dice game]
-
A.
narrativeConsequence
chosen
Indicates that one event, action, or state occurs as a direct result or outcome of another within a narrative sequence.
-
B.
consequenceInText
Indicates that one event, action, or state is presented in the text as a consequence or result of another.
-
C.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
-
D.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
E.
significantEventConsequence
Indicates that one event leads to an important or impactful consequence for another event, state, or entity.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66557c19c8190b511857490bbd423 |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:41 p.m.