Triple

T7308227
Position Surface form Disambiguated ID Type / Status
Subject Chandauli district E168029 entity
Predicate hasHeadquarters P62 FINISHED
Object Chandauli E486439 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: Chandauli | Statement: [Chandauli district, hasHeadquarters, Chandauli]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chandauli
Context triple: [Chandauli district, hasHeadquarters, Chandauli]
  • A. Chandauli chosen
    Chandauli is a town and administrative district headquarters in the eastern Indian state of Uttar Pradesh, known for its agricultural economy and proximity to Varanasi.
  • B. Shahjahanpur
    Shahjahanpur is a prominent city in the Rohilkhand region of Uttar Pradesh, India, known for its historical significance and regional commercial importance.
  • C. Ghazipur
    Ghazipur is a city in the Indian state of Uttar Pradesh, known for its historical significance and as a regional hub in eastern Uttar Pradesh.
  • D. Chhapra
    Chhapra is a city in the Indian state of Bihar, known as the administrative headquarters of Saran district and a regional commercial and transportation hub along the Ganges River.
  • E. Bulandshahr
    Bulandshahr is a city in the Indian state of Uttar Pradesh known for its historical significance and proximity to Delhi within the broader metropolitan region.
  • 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_69c6888d8e3c81909db79714903baf31 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6ebda7b748190a230a22ecea79342 completed March 27, 2026, 8:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8be10c5b081908210981ce9c45bd9 completed March 29, 2026, 5:52 a.m.
Created at: March 27, 2026, 3:01 p.m.