Triple

T23046929
Position Surface form Disambiguated ID Type / Status
Subject Bhima I E573900 entity
Predicate returnedToThrone P73419 FINISHED
Object after withdrawal of Mahmud of Ghazni 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: after withdrawal of Mahmud of Ghazni | Statement: [Bhima I, returnedToThrone, after withdrawal of Mahmud of Ghazni]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: returnedToThrone
Context triple: [Bhima I, returnedToThrone, after withdrawal of Mahmud of Ghazni]
  • A. restoredToThrone chosen
    Indicates that an entity regains a previously held throne or royal position after having lost or been removed from it.
  • B. regainsThroneFrom
    Indicates that one entity takes back control of a throne or rulership position that had been held by another entity.
  • C. lostThroneTo
    Indicates that one entity was previously in possession of a throne or rulership but was defeated or displaced so that another entity took that throne instead.
  • D. lostThroneAgainIn
    Indicates that an entity lost its throne once more, on or during a specified time or event.
  • E. restoredToThroneBy
    Indicates that an entity was returned to a position of rulership or kingship through the actions or intervention of another 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_69e245b9c11481909d06c872214d21af completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18678e5c48190a96a7b4c9c82f8fe completed April 29, 2026, 4:18 a.m.
PD Predicate disambiguation batch_69ef89d5f71881908b9f9d0c8aab278c completed April 27, 2026, 4:07 p.m.
Created at: April 17, 2026, 3:54 p.m.