Triple

T19815235
Position Surface form Disambiguated ID Type / Status
Subject NH 65 E476042 entity
Predicate passesThroughCity P416 FINISHED
Object Indapur 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: Indapur | Statement: [NH 65, passesThroughCity, Indapur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Indapur
Context triple: [NH 65, passesThroughCity, Indapur]
  • A. Indapur chosen
    Indapur is a town in the Indian state of Maharashtra, located within the Pune district and known for its agricultural and regional administrative significance.
  • B. Nadiad
    Nadiad is a city in the Indian state of Gujarat, historically notable as the birthplace of independence leader Sardar Vallabhbhai Patel.
  • C. Raisinghnagar
    Raisinghnagar is a town and administrative center in the northern Indian state of Rajasthan, known for its agricultural economy within the arid region near the India–Pakistan border.
  • D. Sheohar
    Sheohar is a town in the Indian state of Bihar that serves as an administrative and commercial center for the surrounding rural region.
  • E. Alirajpur
    Alirajpur is a town and district headquarters in western Madhya Pradesh, India, known for its predominantly tribal population and vibrant indigenous culture.
  • 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_69d8e51bc4208190a1c57d8c5d1b15e4 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e654f861248190a633dd8d227d9697 completed April 20, 2026, 4:31 p.m.
Created at: April 10, 2026, 1:50 p.m.