Triple

T38634109
Position Surface form Disambiguated ID Type / Status
Subject Nahapana E937533 entity
Predicate instanceOf P0 FINISHED
Object Indo-Scythian ruler C66259 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: Indo-Scythian ruler
Context triple: [Nahapana, instanceOf, Indo-Scythian ruler]
  • A. Indo-Scythian king chosen
    An Indo-Scythian king was a ruler of the Scythian-origin dynasties that established control over parts of northwestern and central South Asia between roughly the 2nd century BCE and 4th century CE, blending Central Asian nomadic traditions with Hellenistic and Indian political and cultural practices.
  • B. Western Kshatrapa ruler
    A Western Kshatrapa ruler was a monarch of the Indo-Scythian dynasty that governed parts of western India (primarily Gujarat and Malwa) between the 1st and 4th centuries CE, known for their distinctive coinage and interactions with contemporary Indian empires.
  • C. Indo-Parthian king
    An Indo-Parthian king is a ruler of the Indo-Parthian dynasty who governed territories in northwestern South Asia and eastern Iran during the early centuries CE, blending Parthian, Hellenistic, and Indian political and cultural traditions.
  • D. Kushan ruler
    A Kushan ruler is a sovereign of the Kushan Empire who governed a vast, multicultural realm in Central and South Asia, overseeing trade along the Silk Road and patronizing diverse religious and artistic traditions.
  • E. Bactrian ruler
    A Bactrian ruler is a sovereign or governing authority who held political power over the ancient region of Bactria, typically during the Hellenistic or early Central Asian historical periods.
  • F. None of above.

Provenance (1 batch)

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_69f76ed5ca3c81909288f61fbf37b359 completed May 3, 2026, 3:50 p.m.
Created at: May 3, 2026, 4:32 p.m.