Triple

T20810597
Position Surface form Disambiguated ID Type / Status
Subject Satna district E512285 entity
Predicate hasRailwayJunction P918 FINISHED
Object Satna 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: Satna Junction | Statement: [Satna district, hasRailwayJunction, Satna Junction]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Satna Junction
Context triple: [Satna district, hasRailwayJunction, Satna Junction]
  • A. Satna Junction chosen
    Satna Junction is a key railway station and transport hub in Madhya Pradesh, India, serving as an important link on major routes of the Indian Railways network.
  • B. Wankaner Junction
    Wankaner Junction is a key railway junction in Gujarat, India, serving as an important stop and interchange on the route between Ahmedabad and Rajkot.
  • C. Badnera Junction
    Badnera Junction is a key railway junction in Maharashtra, India, serving as an important transit point on central Indian rail routes.
  • D. Sonpur Junction
    Sonpur Junction is a major railway station and junction in Bihar, India, serving as an important rail hub in the Saran region.
  • E. Nagda Junction
    Nagda Junction is a major railway junction in Madhya Pradesh, India, serving as an important transit point on key routes connecting western and central India.
  • 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_69e0b4cd25088190b48ca9700cd24efc completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2d27a4881908b34679385d8b94b completed April 21, 2026, 12:20 a.m.
Created at: April 16, 2026, 12:40 p.m.