Triple

T22477931
Position Surface form Disambiguated ID Type / Status
Subject Ghogha E555683 entity
Predicate locatedOnTransportRoute P2409 FINISHED
Object Bhavnagar–Ghogha route NE NERFINISHED

How this triple was built (3 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: Bhavnagar–Ghogha route | Statement: [Ghogha, locatedOnTransportRoute, Bhavnagar–Ghogha route]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bhavnagar–Ghogha route
Context triple: [Ghogha, locatedOnTransportRoute, Bhavnagar–Ghogha route]
  • A. Jabalpur–Nainpur–Gondia route
    The Jabalpur–Nainpur–Gondia route is a railway line in central India that connects Jabalpur in Madhya Pradesh with Gondia in Maharashtra, passing through the important junction town of Nainpur.
  • B. Nagpur–Wardha–Badnera route
    The Nagpur–Wardha–Badnera route is a key railway corridor in Maharashtra, India, connecting major junctions in the Vidarbha region and forming part of an important trunk line for passenger and freight traffic.
  • C. Viramgam–Okha line
    The Viramgam–Okha line is a key broad-gauge railway route in Gujarat, India, connecting inland regions to the coastal town of Okha and serving major stations such as Jamnagar.
  • D. Pune–Daund route
    The Pune–Daund route is a key railway corridor in Maharashtra, India, connecting the city of Pune with the junction town of Daund and serving as an important link for both passenger and freight trains.
  • E. Damoh–Katni line
    The Damoh–Katni line is a railway route in the Indian state of Madhya Pradesh that connects the towns of Damoh and Katni as part of the regional rail network.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Bhavnagar–Ghogha route
Target entity description: The Bhavnagar–Ghogha route is a regional transport corridor in Gujarat, India, connecting the coastal town of Ghogha with the city of Bhavnagar, historically via road and ferry services across the Gulf of Khambhat.
  • A. Jabalpur–Nainpur–Gondia route
    The Jabalpur–Nainpur–Gondia route is a railway line in central India that connects Jabalpur in Madhya Pradesh with Gondia in Maharashtra, passing through the important junction town of Nainpur.
  • B. Nagpur–Wardha–Badnera route
    The Nagpur–Wardha–Badnera route is a key railway corridor in Maharashtra, India, connecting major junctions in the Vidarbha region and forming part of an important trunk line for passenger and freight traffic.
  • C. Viramgam–Okha line
    The Viramgam–Okha line is a key broad-gauge railway route in Gujarat, India, connecting inland regions to the coastal town of Okha and serving major stations such as Jamnagar.
  • D. Pune–Daund route
    The Pune–Daund route is a key railway corridor in Maharashtra, India, connecting the city of Pune with the junction town of Daund and serving as an important link for both passenger and freight trains.
  • E. Damoh–Katni line
    The Damoh–Katni line is a railway route in the Indian state of Madhya Pradesh that connects the towns of Damoh and Katni as part of the regional rail network.
  • F. None of above. chosen

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_69e11e52c2048190952dc5df209b9bed completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15be58ed08190b88706a7cb85616b completed April 29, 2026, 1:16 a.m.
Created at: April 16, 2026, 8:49 p.m.