Triple

T18860803
Position Surface form Disambiguated ID Type / Status
Subject Saurashtra Railway E461305 entity
Predicate formedByMergerOf P77 FINISHED
Object Porbandar State Railway 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: Porbandar State Railway | Statement: [Saurashtra Railway, formedByMergerOf, Porbandar State Railway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Porbandar State Railway
Context triple: [Saurashtra Railway, formedByMergerOf, Porbandar State Railway]
  • A. Bhavnagar State Railway
    Bhavnagar State Railway was a former princely state-owned railway system in the Bhavnagar region of present-day Gujarat, India, that later became part of larger regional railway networks.
  • B. Saurashtra Railway
    Saurashtra Railway was a former Indian railway system that operated in the Saurashtra region of present-day Gujarat before being integrated into the Western Railway zone.
  • C. Porbandar railway station
    Porbandar railway station is a key rail terminus in Gujarat, India, serving the coastal city of Porbandar with regional and long-distance train connections.
  • D. Junagadh State Railway
    Junagadh State Railway was a former princely state-owned railway system in the Junagadh region of present-day Gujarat, India, that later became part of the Saurashtra Railway network.
  • E. Morvi State Railway
    Morvi State Railway was a former princely state-owned railway system in the Morvi region of present-day Gujarat, India, that later became part of the larger Saurashtra Railway 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: Porbandar State Railway
Target entity description: Porbandar State Railway was a former princely-state-owned railway system in the Porbandar region of present-day Gujarat, India, that later became part of larger regional railway networks.
  • A. Bhavnagar State Railway
    Bhavnagar State Railway was a former princely state-owned railway system in the Bhavnagar region of present-day Gujarat, India, that later became part of larger regional railway networks.
  • B. Saurashtra Railway
    Saurashtra Railway was a former Indian railway system that operated in the Saurashtra region of present-day Gujarat before being integrated into the Western Railway zone.
  • C. Porbandar railway station
    Porbandar railway station is a key rail terminus in Gujarat, India, serving the coastal city of Porbandar with regional and long-distance train connections.
  • D. Junagadh State Railway
    Junagadh State Railway was a former princely state-owned railway system in the Junagadh region of present-day Gujarat, India, that later became part of the Saurashtra Railway network.
  • E. Morvi State Railway
    Morvi State Railway was a former princely state-owned railway system in the Morvi region of present-day Gujarat, India, that later became part of the larger Saurashtra Railway 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_69d8dcfb7b9c8190854e7b171b98ea2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c060bfc4819092ac591692a6ccd5 completed April 20, 2026, 5:57 a.m.
Created at: April 10, 2026, 11:57 a.m.