Triple

T7356155
Position Surface form Disambiguated ID Type / Status
Subject Chhattisgarh High Court E169630 entity
Predicate seat P75 FINISHED
Object Bilaspur E205384 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: Bilaspur | Statement: [Chhattisgarh High Court, seat, Bilaspur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bilaspur
Context triple: [Chhattisgarh High Court, seat, Bilaspur]
  • A. Bilaspur chosen
    Bilaspur is a major city in the Indian state of Chhattisgarh, known as an important administrative, commercial, and judicial center.
  • B. Bilaspur
    Bilaspur is a town in the Yamunanagar district of Haryana, India, known as a local commercial and administrative center for surrounding rural areas.
  • C. Hamirpur
    Hamirpur is a town and district headquarters in the Bundelkhand region of Uttar Pradesh, India, known for its location near the confluence of the Yamuna and Betwa rivers.
  • D. Jagdalpur
    Jagdalpur is a city in the Bastar district of Chhattisgarh, India, known for its tribal culture, dense forests, and proximity to major waterfalls and national parks.
  • E. Alirajpur
    Alirajpur is a town and district headquarters in western Madhya Pradesh, India, known for its predominantly tribal population and vibrant indigenous culture.
  • 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_69c68a59f2288190877ca15c19b1e822 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f13a62e48190a2d1781a630aa9f0 completed March 27, 2026, 9:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7faa6a5d88190b969b7783edc67b7 completed March 28, 2026, 3:58 p.m.
Created at: March 27, 2026, 3:05 p.m.