Triple

T6653029
Position Surface form Disambiguated ID Type / Status
Subject Baramati railway station E150867 entity
Predicate locatedIn P40 FINISHED
Object Baramati E28220 NE FINISHED

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: Baramati | Statement: [Baramati railway station, locatedIn, Baramati]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baramati
Context triple: [Baramati railway station, locatedIn, Baramati]
  • A. Baramati chosen
    Baramati is a town in the Pune district of Maharashtra, India, known as an agricultural and industrial hub with historical and political significance.
  • B. Bhusawal
    Bhusawal is a major railway and commercial city in Maharashtra, India, known for its large railway junction and banana-growing region.
  • C. Parbhani
    Parbhani is a significant city in the Marathwada region of Maharashtra, India, known as an important commercial and educational center.
  • D. Ratnagiri
    Ratnagiri is a coastal city in Maharashtra, India, known for its Alphonso mangoes, historic forts, and scenic beaches along the Konkan coast.
  • E. Latur
    Latur is a city in the Marathwada region of western India known for its agricultural economy and for being the epicenter of a devastating earthquake in 1993.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69c687f2c9508190a60b9aad31d3f358 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6b046c1408190af288575e40936d0 completed March 27, 2026, 4:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69c74237905c8190abb9b98a8c603662 completed March 28, 2026, 2:51 a.m.
Created at: March 27, 2026, 2:01 p.m.