Triple
T23170776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devabhuti |
E578852
|
entity |
| Predicate | overthrowResult |
P128623
|
FINISHED |
| Object | end of Shunga rule |
—
|
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: end of Shunga rule | Statement: [Devabhuti, overthrowResult, end of Shunga rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overthrowResult Context triple: [Devabhuti, overthrowResult, end of Shunga rule]
-
A.
overthrown
chosen
Indicates that one entity has removed another from a position of power or authority, typically by force or political upheaval.
-
B.
overthrownIn
Indicates that one entity (such as a government, leader, or regime) was removed from power or defeated in a specific event, context, or time period represented by the other entity.
-
C.
overthrowParticipants
Indicates that the related entities are participants involved in carrying out or attempting an overthrow of an existing authority or regime.
-
D.
overthrowDuration
Indicates the length of time over which an overthrow (such as a coup or removal from power) takes place or remains in effect.
-
E.
overturnedDecisionOf
Indicates that one decision reversed, nullified, or set aside a previous decision.
- 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_69e245fd2a388190b814c0dfa15f7148 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f3007108190bc3c831f81ae1dce |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.