Triple

T11511729
Position Surface form Disambiguated ID Type / Status
Subject Vasudeva I E272927 entity
Predicate capitalCity P204 FINISHED
Object Purushapura E266740 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: Purushapura | Statement: [Vasudeva I, capitalCity, Purushapura]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Purushapura
Context triple: [Vasudeva I, capitalCity, Purushapura]
  • A. Purushapura chosen
    Purushapura was the ancient name of the city now known as Peshawar, a major historical center in the Gandhara region of present-day Pakistan.
  • B. Yasodharapura
    Yasodharapura was the principal royal city of the Khmer Empire, centered around Angkor and serving as a major political and religious hub in medieval Southeast Asia.
  • C. Hastinapura
    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.
  • D. Ujjayini
    Ujjayini is the ancient name of the historic Indian city of Ujjain, a major cultural and religious center known for its prominence in Hindu tradition and astronomy.
  • E. Shajapur
    Shajapur is a town and administrative center in central India known for being the headquarters of Shajapur district in the state of Madhya Pradesh.
  • 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_69d6aae2c3748190bed2ea50dfb160dc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d86db7af688190b68668eb39d382a8 completed April 10, 2026, 3:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69e625055dfc81909a87418a3ed40027 completed April 20, 2026, 1:07 p.m.
Created at: April 8, 2026, 9:36 p.m.