Triple

T12719895
Position Surface form Disambiguated ID Type / Status
Subject Bharatpur Junction railway station E303945 entity
Predicate hasAbbreviation P43 FINISHED
Object BTE E1000097 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: BTE | Statement: [Bharatpur Junction railway station, hasAbbreviation, BTE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: BTE
Context triple: [Bharatpur Junction railway station, hasAbbreviation, BTE]
  • A. BTE chosen
    BTE is the Indian Railways station code for Bharatpur Junction, a key railway station in Rajasthan, India.
  • B. BES
    BES is the international vehicle registration code used for the Caribbean Netherlands islands of Bonaire, Sint Eustatius, and Saba.
  • C. Bt
    Bt is the post-nominal abbreviation for a baronetcy title in the British honours system, indicating that the holder is a baronet.
  • D. BEB
    BEB is the IATA airport code for Benbecula Airport, which serves the island of Benbecula in Scotland’s Outer Hebrides.
  • E. BT1
    BT1 is the central Belfast city centre postcode district in Northern Ireland, covering key commercial and civic areas including Donegall Square.
  • 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_69d7bdf084148190ab9d513dc0735af4 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96411d87481909127e81755f23964 completed April 10, 2026, 8:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69f684e61e7081908dec7958e8bc1125 completed May 2, 2026, 11:12 p.m.
Created at: April 9, 2026, 5:24 p.m.