Triple

T26586102
Position Surface form Disambiguated ID Type / Status
Subject Shashanka E667213 entity
Predicate predecessorAsOverlord P126723 FINISHED
Object Gupta Empire NE NERFINISHED

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: Gupta Empire | Statement: [Shashanka, predecessorAsOverlord, Gupta Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: predecessorAsOverlord
Context triple: [Shashanka, predecessorAsOverlord, Gupta Empire]
  • A. predecessorAsLocalRuler
    Indicates that one entity previously held the position of local ruler immediately before another entity in a given domain or territory.
  • B. predecessorAsSupremeRuler chosen
    Indicates that one entity previously held the position of supreme ruler immediately before another entity.
  • C. predecessorAsPretender
    Indicates that one entity previously held the status or role of pretender (claimant) to a title, position, or throne before another entity.
  • D. predecessorAsDeFactoRuler
    Indicates that one entity previously held actual ruling power over a domain or group, regardless of formal title, before another entity assumed that de facto control.
  • E. predecessorAsHeir
    Indicates that one entity previously held the status of heir before being succeeded by another in that role.
  • 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_69ee9cfb7e548190b60a9031182f5a7e completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f6978fe97081908fe568091ad9b159 completed May 3, 2026, 12:32 a.m.
PD Predicate disambiguation batch_69f69661e6ec8190948251c7516a32ad completed May 3, 2026, 12:27 a.m.
Created at: April 27, 2026, 2:05 a.m.