Triple

T22120226
Position Surface form Disambiguated ID Type / Status
Subject Yeola railway station E546644 entity
Predicate connectsTo P845 FINISHED
Object Kopargaon 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: Kopargaon | Statement: [Yeola railway station, connectsTo, Kopargaon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kopargaon
Context triple: [Yeola railway station, connectsTo, Kopargaon]
  • A. Kopargaon chosen
    Kopargaon is a town in the Ahmednagar district of Maharashtra, India, known as a commercial and transport hub near the pilgrimage city of Shirdi.
  • B. Dharbandora
    Dharbandora is a taluka (administrative subdivision) in the Indian state of Goa, located within the South Goa district.
  • C. Khanapur
    Khanapur is a town in the Indian state of Karnataka known for its scenic surroundings, forested areas, and proximity to the Western Ghats.
  • D. Bagevadi
    Bagevadi is a town in the Indian state of Karnataka, historically renowned as the birthplace of the 12th-century social reformer and philosopher Basava.
  • E. Talegaon
    Talegaon is an industrial town in the Pune Metropolitan Region of Maharashtra, India, known for its manufacturing hubs and proximity to Pune city.
  • 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_69e11e38b3848190ac3a4fa97d56e65a completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f12951fcd48190841319cd879c15cb completed April 28, 2026, 9:40 p.m.
Created at: April 16, 2026, 8:31 p.m.