Triple

T14444030
Position Surface form Disambiguated ID Type / Status
Subject House of Rajasa E358157 entity
Predicate hasMember P10 FINISHED
Object Anusapati E88584 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: Anusapati | Statement: [House of Rajasa, hasMember, Anusapati]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anusapati
Context triple: [House of Rajasa, hasMember, Anusapati]
  • A. Anusapati chosen
    Anusapati was a 13th-century Javanese king who ruled the Singhasari Kingdom in East Java, Indonesia.
  • B. Ashwapati
    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. Upatiṣya
    Upatiṣya is the personal name of Śāriputra, one of the Buddha’s foremost disciples renowned for his wisdom in early Buddhism.
  • D. Wiradhuri
    Wiradhuri refers to the Wiradjuri people, one of the largest Aboriginal groups in New South Wales, Australia, known for their rich cultural traditions and strong connection to the land.
  • E. Pujali
    Pujali is a small town and municipality in the Indian state of West Bengal, situated near Kolkata along the Hooghly River.
  • 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_69d82794dfa081909b9134ad2e32244b completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de915e76f481909fe9462f964b5b1c completed April 14, 2026, 7:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd5bdd0f388190870ddd01f66d3e99 completed May 8, 2026, 3:43 a.m.
Created at: April 10, 2026, 1:19 a.m.