Triple

T19103870
Position Surface form Disambiguated ID Type / Status
Subject Kurukshetra tirtha circuit E467602 entity
Predicate hasPart P35 FINISHED
Object Jyotisar 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: Jyotisar | Statement: [Kurukshetra tirtha circuit, hasPart, Jyotisar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jyotisar
Context triple: [Kurukshetra tirtha circuit, hasPart, Jyotisar]
  • A. Jyotisar chosen
    Jyotisar is a revered pilgrimage site in Haryana, India, traditionally regarded as the place where Lord Krishna delivered the Bhagavad Gita to Arjuna.
  • B. Singhwara
    Singhwara is a town located in the Darbhanga district of the Indian state of Bihar.
  • C. Kundarki
    Kundarki is a notable town in the Moradabad district of Uttar Pradesh, India, serving as a local hub for trade and administration.
  • D. Surya Kund
    Surya Kund is a large, intricately stepped ritual tank at the Modhera Sun Temple in Gujarat, India, used historically for ceremonial ablutions before worship.
  • E. Surya Kund
    Surya Kund is a famous natural hot water spring near the Yamunotri temple in Uttarakhand, India, where pilgrims traditionally cook offerings and perform ritual baths.
  • 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_69d8dd05ac4c8190b1967d8f97f3fb2f completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e36f84048190a62c52411eb55411 completed April 20, 2026, 8:27 a.m.
Created at: April 10, 2026, 12:04 p.m.