Triple

T5747409
Position Surface form Disambiguated ID Type / Status
Subject Majha region E126767 entity
Predicate containsCity P294 FINISHED
Object Gurdaspur E333270 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: Gurdaspur | Statement: [Majha region, containsCity, Gurdaspur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gurdaspur
Context triple: [Majha region, containsCity, Gurdaspur]
  • A. Gurdaspur chosen
    Gurdaspur is a city in the northern Indian state of Punjab, known for its agricultural surroundings and proximity to the India–Pakistan border.
  • B. Hoshiarpur
    Hoshiarpur is a historic city in the Indian state of Punjab, known for its cultural heritage, educational institutions, and agricultural surroundings.
  • C. Nawanshahr
    Nawanshahr is a town and district headquarters in the Doaba region of Punjab, India, known for its agricultural base and significant Punjabi diaspora.
  • D. Faridkot
    Faridkot is a historic town and district headquarters in the Malwa region of Punjab, India, known for its cultural heritage and agricultural surroundings.
  • E. Ferozepur
    Ferozepur is a historic city in the Indian state of Punjab, known for its strategic location near the India–Pakistan border and its role in various military and independence-era events.
  • 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_69c0083179548190b384b0bf3c08ca4d completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02885b0288190835809681a364b1f completed March 22, 2026, 5:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0b0c0dd948190a39c714026a228b0 completed March 23, 2026, 3:17 a.m.
Created at: March 22, 2026, 3:48 p.m.