Triple

T19730906
Position Surface form Disambiguated ID Type / Status
Subject Panchala E473849 entity
Predicate containsCity P294 FINISHED
Object Ahichhatra 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: Ahichhatra | Statement: [Panchala, containsCity, Ahichhatra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ahichhatra
Context triple: [Panchala, containsCity, Ahichhatra]
  • A. Ahichhatra chosen
    Ahichhatra was an ancient city in northern India that served as a major political and cultural center of the Panchala kingdom.
  • B. Hanumangarh
    Hanumangarh is a town in the northern Indian state of Rajasthan, known for serving as an administrative and commercial center near the Ghaggar River and the Punjab border.
  • C. Betapur
    Betapur is a small settlement located on Middle Andaman Island in the Andaman and Nicobar Islands of India.
  • D. Orchha
    Orchha is a historic town in central India renowned for its medieval palaces, temples, and riverside cenotaphs built by the Bundela Rajput rulers.
  • E. Ajodhya Hills
    Ajodhya Hills is a scenic hill range in West Bengal, India, known for its forested landscapes, waterfalls, tribal villages, and trekking opportunities.
  • 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_69d8e517ebd48190979ee76723bcfadf completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e649fbeaf081909e9356229eaf84dd completed April 20, 2026, 3:45 p.m.
Created at: April 10, 2026, 1:47 p.m.