Triple

T4872022
Position Surface form Disambiguated ID Type / Status
Subject NH 44 E109106 entity
Predicate connectsCity P4245 FINISHED
Object Sonipat E340091 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: Sonipat | Statement: [NH 44, connectsCity, Sonipat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sonipat
Context triple: [NH 44, connectsCity, Sonipat]
  • A. Sonipat chosen
    Sonipat is a rapidly developing city in the northern Indian state of Haryana that forms part of the extended urban and economic area around Delhi.
  • B. Bhind
    Bhind is a city in the northern part of the Indian state of Madhya Pradesh, known as an administrative and commercial center of the region.
  • C. Etawah
    Etawah is a city in the Indian state of Uttar Pradesh, known for its location near the Chambal ravines and as an important regional administrative and transportation center.
  • D. Palwal
    Palwal is a city in the Indian state of Haryana that forms part of the extended urban area surrounding Delhi.
  • E. Sheopur
    Sheopur is a town and district headquarters in the northern part of the Indian state of Madhya Pradesh, known for its proximity to the Kuno National Park and its largely rural, agrarian surroundings.
  • 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_69bd440d96a48190b0c87069adef2af1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6d9e27908190a0c4540ee2559c4b completed March 20, 2026, 3:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69bea467648c81909ca14744aeeee719 completed March 21, 2026, 2 p.m.
Created at: March 20, 2026, 1:27 p.m.