Triple

T16071030
Position Surface form Disambiguated ID Type / Status
Subject Rohtak Junction railway station E389859 entity
Predicate connectedTo P37 FINISHED
Object Rewari E324204 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: Rewari | Statement: [Rohtak Junction railway station, connectedTo, Rewari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rewari
Context triple: [Rohtak Junction railway station, connectedTo, Rewari]
  • A. Rewari chosen
    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.
  • B. Bhiwani
    Bhiwani is a city in the Indian state of Haryana known as a regional educational and political hub.
  • C. Rohtak
    Rohtak is a major city in the Indian state of Haryana, known as an educational and administrative center within the National Capital Region.
  • D. 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.
  • E. Ambala
    Ambala is a historic city and important military and transportation hub in the northern Indian state of Haryana.
  • 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_69d86daf32ec8190a8c0466c8f49c3c0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e183be909c8190ac6c37ab047151ae completed April 17, 2026, 12:50 a.m.
NED1 Entity disambiguation (via context triple) batch_6a005809cbf08190b35f2c820793163c completed May 10, 2026, 10:03 a.m.
Created at: April 10, 2026, 4:57 a.m.