Triple

T19172658
Position Surface form Disambiguated ID Type / Status
Subject Shunga period E469363 entity
Predicate instanceOf P0 FINISHED
Object ancient Indian historical era C138 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: ancient Indian historical era
Context triple: [Shunga period, instanceOf, ancient Indian historical era]
  • A. medieval Indian period
    The medieval Indian period refers to the historical era roughly from the 8th to the 18th century CE in the Indian subcontinent, marked by the rise and fall of regional kingdoms and empires, extensive cultural and religious synthesis, and significant developments in art, architecture, literature, and trade.
  • B. era in South Indian history
    An era in South Indian history is a distinct time period characterized by specific dynasties, cultural developments, political structures, and socio-economic patterns that shaped the region’s historical trajectory.
  • C. Itihasa
    Itihasa is a conceptual class representing ancient Indian historical-epic narratives that blend myth, legend, cultural memory, and moral instruction, exemplified by works like the Mahabharata and Ramayana.
  • D. historical period chosen
    A historical period is a span of time characterized by distinct social, political, cultural, or technological conditions that differentiate it from other eras in history.
  • E. event in Indian history
    An event in Indian history is a significant occurrence or series of actions within the Indian subcontinent’s past that influenced its political, social, cultural, or economic development.
  • 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_69d8dd09d5a081909ae43c286651ae5a completed April 10, 2026, 11:20 a.m.
Created at: April 10, 2026, 12:06 p.m.