Triple

T18476699
Position Surface form Disambiguated ID Type / Status
Subject Dhrishtadyumna E451451 entity
Predicate category P87 FINISHED
Object Panchala princes 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: Panchala princes | Statement: [Dhrishtadyumna, category, Panchala princes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Panchala princes
Context triple: [Dhrishtadyumna, category, Panchala princes]
  • A. King of Panchala chosen
    King of Panchala is a royal title in the Indian epic Mahabharata, most notably held by Drupada, the ruler of the ancient kingdom of Panchala.
  • B. Pavanputra
    Pavanputra is a revered epithet of the Hindu deity Hanuman, highlighting his divine parentage as the son of the wind god.
  • C. Dikpalas
    The Dikpalas are a group of Hindu deities regarded as the guardians of the directions, each presiding over and protecting a specific cardinal or intercardinal point of the cosmos.
  • D. Sindhuraja
    Sindhuraja was a medieval Indian king of the Paramara dynasty, known for consolidating and expanding its power in central India.
  • 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 (2 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_69d8d38465a0819099b9b42d2a662ac1 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e53063c0108190be71247567b5241b completed April 19, 2026, 7:43 p.m.
Created at: April 10, 2026, 11:35 a.m.