Triple

T7469875
Position Surface form Disambiguated ID Type / Status
Subject Baghpat region E176473 entity
Predicate hasRailConnectivityWith P58937 FINISHED
Object Saharanpur E453695 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: Saharanpur | Statement: [Baghpat region, hasRailConnectivityWith, Saharanpur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saharanpur
Context triple: [Baghpat region, hasRailConnectivityWith, Saharanpur]
  • A. Saharanpur chosen
    Saharanpur is a city in the Indian state of Uttar Pradesh known as a commercial and transportation hub, particularly for its wood carving industry and agricultural trade.
  • B. Ambala
    Ambala is a historic city and important military and transportation hub in the northern Indian state of Haryana.
  • C. Rampur
    Rampur is a small settlement located on Middle Andaman Island in the Andaman and Nicobar Islands of India.
  • D. Rampur
    Rampur is a prominent city in the Rohilkhand region of Uttar Pradesh, India, known historically for its princely state heritage and distinctive Rampuri culture.
  • E. Yamunanagar
    Yamunanagar is an industrial city in the Indian state of Haryana, known for its plywood, paper, and metal industries and its proximity to the Yamuna River.
  • 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_69c69f223fd88190b4c69b95d7cbeeda completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f4ec85488190a1f7fb913e0fbe35 completed March 27, 2026, 9:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8eef3b7a88190bb42b5f93ce2daba completed March 29, 2026, 9:20 a.m.
Created at: March 27, 2026, 3:41 p.m.