Triple

T17413199
Position Surface form Disambiguated ID Type / Status
Subject Ahmedpur East E423419 entity
Predicate roadConnection P385 FINISHED
Object Hasilpur NE NERFINISHED

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: Hasilpur | Statement: [Ahmedpur East, roadConnection, Hasilpur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hasilpur
Context triple: [Ahmedpur East, roadConnection, Hasilpur]
  • A. Hasilpur chosen
    Hasilpur is a city in the Bahawalpur District of southern Punjab, Pakistan, known as a regional commercial and agricultural center.
  • B. Jagdishpur
    Jagdishpur is a town in the Bhojpur district of Bihar, India, historically known as the ancestral estate of the 19th-century freedom fighter Kunwar Singh.
  • C. Jagdishpur
    Jagdishpur is a town in the Amethi district of Uttar Pradesh, India, known for its industrial area and historical significance in the region.
  • D. Mushalpur
    Mushalpur is a small town in the Indian state of Assam that serves as an administrative and commercial center for the surrounding rural region.
  • E. Mahipalpur
    Mahipalpur is an urban village and commercial area in Delhi, India, located near Indira Gandhi International Airport and known for its hotels, transport hubs, and proximity to major highways.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889d7d27c819088486ce3f0627fa1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43b0c12b881908b2ddc13678c7a75 completed April 19, 2026, 2:16 a.m.
Created at: April 10, 2026, 5:46 a.m.