Triple

T14579654
Position Surface form Disambiguated ID Type / Status
Subject Bahadurgarh E342152 entity
Predicate hasBusConnectivity P39381 FINISHED
Object Jhajjar E394860 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: Jhajjar | Statement: [Bahadurgarh, hasBusConnectivity, Jhajjar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jhajjar
Context triple: [Bahadurgarh, hasBusConnectivity, Jhajjar]
  • A. Jhajjar district chosen
    Jhajjar district is an administrative district in the Indian state of Haryana, known for its predominantly rural character and proximity to the National Capital Region.
  • B. Rewari
    Rewari is a historic city in the Indian state of Haryana, located near Delhi and known for its brass industry and strategic position in northern India.
  • C. Saharanpur
    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.
  • D. Rampur
    Rampur is a small settlement located on Middle Andaman Island in the Andaman and Nicobar Islands of India.
  • E. 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.
  • 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_69d822ddc0f081909cd8163c7de298cd completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb3f6f78c81908a30ecb4c025299d completed April 14, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fda91437e08190a41683f1777a8507 completed May 8, 2026, 9:12 a.m.
Created at: April 10, 2026, 1:24 a.m.