Triple

T5616651
Position Surface form Disambiguated ID Type / Status
Subject Saketa E147493 entity
Predicate partOf P40 FINISHED
Object Kosala E449560 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: Kosala | Statement: [Saketa, partOf, Kosala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kosala
Context triple: [Saketa, partOf, Kosala]
  • A. Kosala chosen
    Kosala is an ancient Indian kingdom in Hindu epic tradition, most prominently known as the realm ruled by Lord Rama with its capital at Ayodhya.
  • B. Panchala
    Panchala was an ancient Indian kingdom of the Mahabharata era, known for its powerful rulers and as the homeland of Draupadi.
  • C. Kishkindha
    Kishkindha is the mythical monkey kingdom ruled by Sugriva in the Indian epic Ramayana, where Rama forms an alliance with the vanara army to search for Sita.
  • D. Kosala kingdom
    The Kosala kingdom was an ancient Indian realm in the Ganges plain, prominent in Hindu epics and early Buddhist texts as a major political and cultural center.
  • E. Braj
    Braj is a culturally significant region in northern India traditionally associated with the life and legends of the Hindu deity Krishna.
  • 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_69c00905d4588190bd967842bbcf2219 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c021da7f848190bb1cd0270ad6398f completed March 22, 2026, 5:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69c04d55b95c8190a5f3e2c05249c136 completed March 22, 2026, 8:13 p.m.
Created at: March 22, 2026, 3:39 p.m.