Triple

T25490243
Position Surface form Disambiguated ID Type / Status
Subject Nripa Kama II E638817 entity
Predicate successorDynastyBecame P168031 FINISHED
Object major power in the Deccan region 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: major power in the Deccan region | Statement: [Nripa Kama II, successorDynastyBecame, major power in the Deccan region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: successorDynastyBecame
Context triple: [Nripa Kama II, successorDynastyBecame, major power in the Deccan region]
  • A. successorDynasty
    Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
  • B. successorDynastyFoundedBy
    Indicates that the successor dynasty was established or founded by the referenced person or group.
  • C. successorDynastyOrigin
    Indicates the place or cultural-geographic origin from which a successor dynasty arises in relation to its predecessor.
  • D. dynasticSuccessionChangedBy
    Indicates that a change or disruption has occurred in the established line of dynastic succession due to the influence or action of the related entity.
  • E. successorAsEasternRuler
    Indicates that one entity became the next ruler of an eastern domain or territory after another entity.
  • F. None of above. chosen

Provenance (4 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_69e75dbbd2a88190b70e1e645de14b9a completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f673633d288190b52ceb9f8a057c44 completed May 2, 2026, 9:57 p.m.
PD Predicate disambiguation batch_69f66ec3d3d48190ab2f2b71939e572e completed May 2, 2026, 9:38 p.m.
PDg Predicate description generation batch_69f67256d064819094be04fc1bbbc635 completed May 2, 2026, 9:53 p.m.
Created at: April 21, 2026, 2:38 p.m.