Triple

T14386055
Position Surface form Disambiguated ID Type / Status
Subject Indrapura E356725 entity
Predicate successorCapital P30709 FINISHED
Object Vijaya E356726 NE 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: Vijaya | Statement: [Indrapura, successorCapital, Vijaya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vijaya
Context triple: [Indrapura, successorCapital, Vijaya]
  • A. Vijaya chosen
    Vijaya was the principal royal and political center of the historical Champa kingdom in what is now central Vietnam.
  • B. Vijaya
    Vijaya is a relatively obscure figure in the Mahabharata tradition known primarily as the wife of Sahadeva, the youngest of the Pandava brothers.
  • C. Sanjaya
    Sanjaya was an early Javanese king traditionally regarded as the founder of the Mataram (Medang) Kingdom and the Sanjaya dynasty in Central Java.
  • D. Sanjaya
    Sanjaya is the charioteer and seer in the Mahabharata who, granted divine vision, narrates the events of the Kurukshetra war to the blind king Dhritarashtra.
  • E. Santivarma
    Santivarma was a ruler of the ancient Kadamba dynasty, an early Kannada-speaking royal house that governed parts of present-day Karnataka in southern India.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d827927c988190ad98bb0360981783 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de9025cff881908c08224d90d9f750 completed April 14, 2026, 7:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd5bc0c9708190b5025e9675e0e925 completed May 8, 2026, 3:42 a.m.
Created at: April 10, 2026, 1:16 a.m.