Triple

T14475829
Position Surface form Disambiguated ID Type / Status
Subject Kaithal E358967 entity
Predicate hasNearbyMajorCity P1982 FINISHED
Object Karnal E389853 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: Karnal | Statement: [Kaithal, hasNearbyMajorCity, Karnal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Karnal
Context triple: [Kaithal, hasNearbyMajorCity, Karnal]
  • A. Karnal chosen
    Karnal is a historic city in the Indian state of Haryana, known for its agricultural significance and strategic location along the Grand Trunk Road between Delhi and Chandigarh.
  • B. Barnala
    Barnala is a city in the Malwa region of Punjab, India, known as an administrative and commercial center for the surrounding agricultural area.
  • C. Sheohar
    Sheohar is a town in the Indian state of Bihar that serves as an administrative and commercial center for the surrounding rural region.
  • D. Jullundur
    Jullundur is the former English spelling of Jalandhar, a major city in the Indian state of Punjab.
  • E. Nadiad
    Nadiad is a city in the Indian state of Gujarat, historically notable as the birthplace of independence leader Sardar Vallabhbhai Patel.
  • 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_69d827966698819082e140837737501d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de91fc1fc48190842b09aa03ba79f8 completed April 14, 2026, 7:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd6d8ccd608190afd23c903cd5686a completed May 8, 2026, 4:58 a.m.
Created at: April 10, 2026, 1:20 a.m.