Triple

T23240126
Position Surface form Disambiguated ID Type / Status
Subject Matsya E581416 entity
Predicate capital P234 FINISHED
Object Viratanagara 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: Viratanagara | Statement: [Matsya, capital, Viratanagara]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Viratanagara
Context triple: [Matsya, capital, Viratanagara]
  • A. Varanavata chosen
    Varanavata is the town in the Mahabharata where the Kauravas plotted to kill the Pandavas by burning the lac palace.
  • B. Valmikinagar
    Valmikinagar is a town in Bihar, India, known for its proximity to the Valmiki Tiger Reserve and its location along the Gandak River near the Indo-Nepal border.
  • C. Banavasi
    Banavasi is an ancient town in Karnataka, India, historically significant as an early capital of the Kadamba dynasty and a major center of early Kannada culture and inscriptions.
  • D. Tanguturi
    Tanguturi is the given name of T. Prakasam, a prominent Indian freedom fighter and former Chief Minister of the Madras Presidency and Andhra State.
  • E. Pavapuri
    Pavapuri is a revered Jain pilgrimage site in Bihar, India, best known as the place where Mahavira, the 24th Tirthankara, attained nirvana.
  • 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_69e2460556f88190be1744a84a84173f completed April 17, 2026, 2:39 p.m.
NER Named-entity recognition batch_69f192ecc7e481908cac59df5c0deea1 completed April 29, 2026, 5:11 a.m.
Created at: April 17, 2026, 4:10 p.m.