Triple

T27280205
Position Surface form Disambiguated ID Type / Status
Subject Vallabhi E688309 entity
Predicate predecessorPowerContext P169915 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: [Vallabhi, predecessorPowerContext, Gupta Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: predecessorPowerContext
Context triple: [Vallabhi, predecessorPowerContext, Gupta Empire]
  • A. predecessorPowerBaseOf chosen
    Indicates that one entity previously served as the primary source of authority, support, or influence for another entity before a later or current power base.
  • B. successorPowerContext
    Indicates that one entity holds or exercises power or authority as a successor within a particular contextual or situational framework.
  • C. predecessorOfficeContext
    Indicates that one office or position directly preceded another within a specific organizational or temporal context.
  • D. predecessorUser
    Indicates that one user previously held a role, position, or state that is now held by another user, making the first user the predecessor of the second.
  • E. predecessorStateContext
    Indicates that one state serves as the immediately preceding state within a given contextual sequence or process.
  • 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_69ef3558cf8881909595ef89daf6e14a completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f6b49436b0819094e21603054d05d4 completed May 3, 2026, 2:36 a.m.
PD Predicate disambiguation batch_69f6b3a5fd8481909433e923c5e24e55 completed May 3, 2026, 2:32 a.m.
Created at: April 27, 2026, 11:06 a.m.