Triple

T4872017
Position Surface form Disambiguated ID Type / Status
Subject NH 44 E109106 entity
Predicate connectsCity P4245 FINISHED
Object Pathankot E95953 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: Pathankot | Statement: [NH 44, connectsCity, Pathankot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pathankot
Context triple: [NH 44, connectsCity, Pathankot]
  • A. Pathankot chosen
    Pathankot is a city in the northern Indian state of Punjab, known as a strategic transport hub near the borders of Jammu and Kashmir and Himachal Pradesh.
  • B. Pathankot Airport
    Pathankot Airport is a regional airport in Punjab, India, serving the city of Pathankot and nearby areas with limited commercial and military aviation operations.
  • C. Ayodhya Cantt
    Ayodhya Cantt is a major railway station serving the city of Ayodhya in Uttar Pradesh, India, connecting it to key destinations across the country.
  • D. Pathankot Junction
    Pathankot Junction is a major railway station and transit hub in Punjab, India, serving as a key gateway to the Himalayan regions of Himachal Pradesh and Jammu & Kashmir.
  • E. Shimla Airport
    Shimla Airport is a small domestic airport in the Indian state of Himachal Pradesh that serves the hill station city of Shimla and its surrounding region.
  • 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_69bd440d96a48190b0c87069adef2af1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6d9e27908190a0c4540ee2559c4b completed March 20, 2026, 3:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69be67f1ca1881909a7412087fa0efab completed March 21, 2026, 9:42 a.m.
Created at: March 20, 2026, 1:27 p.m.