Triple

T1223250
Position Surface form Disambiguated ID Type / Status
Subject Maurya Empire E26270 entity
Predicate notableRuler P22 FINISHED
Object Ashoka E126524 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: Ashoka | Statement: [Maurya Empire, notableRuler, Ashoka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashoka
Context triple: [Maurya Empire, notableRuler, Ashoka]
  • A. Ashoka chosen
    Ashoka was a 3rd-century BCE Mauryan emperor of India renowned for his vast empire, conversion to Buddhism, and promotion of nonviolence and moral governance.
  • B. Chandragupta Maurya
    Chandragupta Maurya was the founder of one of ancient India’s largest and most powerful empires, ruling from Pataliputra and laying the foundations for the Mauryan dynasty’s political and administrative systems.
  • C. Bindusara
    Bindusara was the second emperor of the Maurya dynasty in ancient India, known for consolidating and expanding the vast empire established by his father Chandragupta Maurya.
  • D. Rajasuya
    Rajasuya is an ancient Vedic royal consecration ritual performed to legitimize and exalt a king’s sovereignty and supreme status.
  • E. Dasharatha
    Dasharatha is the legendary king of Ayodhya in Hindu mythology, best known as the father of Lord Rama.
  • 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_69a49484688c8190a1bf285eb396a8b6 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4be233fd88190996faf4105c0b8d7 completed March 1, 2026, 10:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69aca2eb158081909f1175d8f4daaa96 completed March 7, 2026, 10:12 p.m.
Created at: March 1, 2026, 7:47 p.m.