Triple

T18538397
Position Surface form Disambiguated ID Type / Status
Subject Midnapore railway station E453023 entity
Predicate connectsTo P845 FINISHED
Object Adra Junction 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: Adra Junction | Statement: [Midnapore railway station, connectsTo, Adra Junction]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Adra Junction
Context triple: [Midnapore railway station, connectsTo, Adra Junction]
  • A. Adra Junction chosen
    Adra Junction is a key railway junction in West Bengal, India, serving as an important operational and connectivity hub in the Indian Railways network.
  • B. Miraj Junction
    Miraj Junction is a key railway hub in Maharashtra, India, serving as an important interchange point connecting routes between Pune, Goa, and Karnataka.
  • C. Achhnera Junction
    Achhnera Junction is a key railway junction in Uttar Pradesh, India, serving as an important connecting point between Agra and several regional routes.
  • D. Sikar Junction
    Sikar Junction is a major railway station in Rajasthan, India, serving the city of Sikar as an important regional rail hub.
  • E. Sonpur Junction
    Sonpur Junction is a major railway station and junction in Bihar, India, serving as an important rail hub in the Saran region.
  • 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_69d8d387b5548190aa030dad2cb4947e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e534030bd88190b25b95305a12a0c1 completed April 19, 2026, 7:58 p.m.
Created at: April 10, 2026, 11:37 a.m.