Triple

T19594474
Position Surface form Disambiguated ID Type / Status
Subject Ashwapati E470315 entity
Predicate nameVariant P744 FINISHED
Object Aśvapati 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: Aśvapati | Statement: [Ashwapati, nameVariant, Aśvapati]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aśvapati
Context triple: [Ashwapati, nameVariant, Aśvapati]
  • A. Aśvajit
    Aśvajit was one of the Buddha’s early disciples, traditionally remembered as the monk whose brief teaching led to the conversion of Śāriputra.
  • B. Ashwapati chosen
    Ashwapati is a king in the Hindu epic Ramayana, best known as the ruler of the kingdom of Kekaya and the father of Queen Kaikeyi.
  • C. Asvabhahu
    Asvabhahu was a literary pseudonym used by King Vajiravudh (Rama VI) of Siam for some of his written works.
  • D. Puspadanta
    Puspadanta was a prominent Jain monk and poet known for composing important Apabhramsha-language works such as the Mahapurana.
  • E. Dronasimha
    Dronasimha was a ruler of the Maitraka dynasty of western India, known from inscriptions as one of the early kings who helped consolidate Maitraka power in the region.
  • 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_69d8e510024481908415c0d616fa6186 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e640793cd88190b9b84491bfb2493f completed April 20, 2026, 3:04 p.m.
Created at: April 10, 2026, 1:43 p.m.