Triple

T942038
Position Surface form Disambiguated ID Type / Status
Subject Rama Navami E20325 entity
Predicate majorCelebrationSite P7849 FINISHED
Object Sitamarhi E51542 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: Sitamarhi | Statement: [Rama Navami, majorCelebrationSite, Sitamarhi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sitamarhi
Context triple: [Rama Navami, majorCelebrationSite, Sitamarhi]
  • A. Sitamarhi district chosen
    Sitamarhi district is an administrative region in the Indian state of Bihar, known for its cultural heritage and association with the Maithili-speaking Mithila region.
  • B. Burhanpur
    Burhanpur is a historic city in central India known for its Mughal-era architecture and strategic location on the banks of the Tapti River.
  • C. Bhagyanagar
    Bhagyanagar is an old historical name for the Indian city now known as Hyderabad.
  • D. Dibrugarh
    Dibrugarh is a prominent city in northeastern India known as a major commercial and industrial hub of Assam, especially for its tea industry and oil and natural gas sectors.
  • E. Gorakhpur
    Gorakhpur is a prominent city in northern India known as a regional commercial, transportation, and cultural hub near the border with Nepal.
  • 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_69a493b0270c81909e6c9ce310f6aa55 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b74fc204819083dbed5c19c4bc15 completed March 1, 2026, 10:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac16fdd37c81909262c1cc271cdd21 completed March 7, 2026, 12:15 p.m.
Created at: March 1, 2026, 7:40 p.m.