Triple

T902919
Position Surface form Disambiguated ID Type / Status
Subject Arjuna E19483 entity
Predicate kingdomAssociatedWith P20193 FINISHED
Object Hastinapura E114385 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: Hastinapura | Statement: [Arjuna, kingdomAssociatedWith, Hastinapura]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hastinapura
Context triple: [Arjuna, kingdomAssociatedWith, Hastinapura]
  • A. Hastinapura chosen
    Hastinapura is the ancient royal capital of the Kuru kingdom in Indian epic tradition, serving as the primary political and familial setting of the Mahabharata.
  • B. Dahanapura
    Dahanapura was the principal city and political center of the historical Kediri Kingdom in Java.
  • C. Dharmakshetra
    Dharmakshetra is the sacred battlefield of Kurukshetra in the Indian epic Mahabharata, revered as a holy site where the Bhagavad Gita was spoken.
  • D. Mathura
    Mathura is an ancient city in northern India revered in Hinduism as the birthplace of Lord Krishna and a major pilgrimage center.
  • E. Magahi
    Magahi is an Eastern Indo-Aryan language spoken primarily in the Indian state of Bihar and surrounding regions.
  • 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_69a4939e889c8190ac148b3ac1a7f90b completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b2b9339081909af5ab231be39bb0 completed March 1, 2026, 9:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac6611ad508190aac3a6f15a63bbe8 completed March 7, 2026, 5:53 p.m.
Created at: March 1, 2026, 7:39 p.m.