Triple

T15094790
Position Surface form Disambiguated ID Type / Status
Subject Panipat Junction E360510 entity
Predicate connectsTo P845 FINISHED
Object Chandigarh E15653 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: Chandigarh | Statement: [Panipat Junction, connectsTo, Chandigarh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chandigarh
Context triple: [Panipat Junction, connectsTo, Chandigarh]
  • A. Chandigarh chosen
    Chandigarh is a planned city in northern India, renowned for its modernist architecture and urban design largely conceived by the Swiss-French architect Le Corbusier.
  • B. Mohali
    Mohali is a planned city in the Indian state of Punjab, forming part of the Chandigarh Tricity region and known for its IT industry and international cricket stadium.
  • C. Shimla
    Shimla is a popular hill station and the capital city of Himachal Pradesh, known for its colonial-era architecture and scenic Himalayan surroundings in northern India.
  • D. Ludhiana
    Ludhiana is a major industrial city in the Indian state of Punjab, known especially for its textile and hosiery manufacturing.
  • E. Jammu
    Jammu is a historically significant city and region in northern India, known as the winter capital of Jammu and Kashmir and a former stronghold of Dogra rulers.
  • 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_69d85a035aa88190b52a139d3a1b7b6d completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0054571a48190a57055c0d6e90f82 completed April 15, 2026, 9:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69fedd24523081908cf12a5d6bdd634d completed May 9, 2026, 7:07 a.m.
Created at: April 10, 2026, 3:04 a.m.