Triple

T12952425
Position Surface form Disambiguated ID Type / Status
Subject Sangrur district E309923 entity
Predicate administrativeHeadquarters P62 FINISHED
Object Sangrur E309922 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: Sangrur | Statement: [Sangrur district, administrativeHeadquarters, Sangrur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sangrur
Context triple: [Sangrur district, administrativeHeadquarters, Sangrur]
  • A. Sangrur chosen
    Sangrur is a city in the Indian state of Punjab known as an agricultural and administrative center within the Malwa region.
  • B. Jagraon
    Jagraon is a historic town in the Indian state of Punjab, known for its agricultural trade and cultural significance in the Malwa region.
  • C. Indergarh
    Indergarh is a small town located in the Bundi district of the Indian state of Rajasthan.
  • D. Barwala
    Barwala is a prominent town in the Hisar district of Haryana, India, known as a local commercial and administrative center for surrounding rural areas.
  • E. Kachh
    Kachh is a traditional Sikh undergarment and one of the five articles of faith (the Five Ks) worn by initiated Sikhs.
  • 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_69d7bdfb57a88190836b743e2825feca completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d97e1edcdc8190a702c2a5ea58cc67 completed April 10, 2026, 10:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69f73051273c81909eb91c923f37557e completed May 3, 2026, 11:24 a.m.
Created at: April 9, 2026, 5:43 p.m.