Triple

T12118498
Position Surface form Disambiguated ID Type / Status
Subject Sikar Junction E288627 entity
Predicate connectsTo P845 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: [Sikar Junction, connectsTo, Rewari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rewari
Context triple: [Sikar Junction, connectsTo, 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. Rohtak
    Rohtak is a major city in the Indian state of Haryana, known as an educational and administrative center within the National Capital Region.
  • 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. Ambala
    Ambala is a historic city and important military and transportation hub in the northern Indian state of Haryana.
  • E. Faridabad
    Faridabad is a major industrial city in northern India known for its manufacturing sector and its location within the National Capital Region near New Delhi.
  • 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_69d6ab4a5c448190a110d1273314b21a completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d915760d208190b68f5e024b3676ba completed April 10, 2026, 3:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f682397c819085a86a98e079660b completed May 2, 2026, 1:05 p.m.
Created at: April 8, 2026, 9:49 p.m.