Triple
T25297110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhallaladeva |
E634243
|
entity |
| Predicate | causeOfDownfallInStory |
P26452
|
FINISHED |
| Object | exposed tyranny |
—
|
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: exposed tyranny | Statement: [Bhallaladeva, causeOfDownfallInStory, exposed tyranny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDownfallInStory Context triple: [Bhallaladeva, causeOfDownfallInStory, exposed tyranny]
-
A.
causeOfDownfall
chosen
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
B.
causeInStory
Indicates that one event, action, or state functions as the cause of another within the narrative structure of a story.
-
C.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
D.
سبب النزول
Indicates the relationship of being the specific cause, event, or circumstance that led to the revelation of a particular Quranic verse or passage.
-
E.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 1:22 p.m.