Triple

T21878899
Position Surface form Disambiguated ID Type / Status
Subject British Rail Class 68 E540224 entity
Predicate safetySystem P840 FINISHED
Object GSM-R 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: GSM-R | Statement: [British Rail Class 68, safetySystem, GSM-R]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GSM-R
Context triple: [British Rail Class 68, safetySystem, GSM-R]
  • A. GSM-R chosen
    GSM-R is a digital radio communication system used across European railways to provide secure voice and data links between trains and railway control centers.
  • B. GSM
    GSM is a second-generation (2G) digital mobile communication standard that became the global foundation for cellular voice and basic data services.
  • C. GSM
    GSM is the common abbreviation for Great St Mary’s Church, the historic University Church located in the center of Cambridge, England.
  • D. GSM
    GSM is the three-letter IATA airport code assigned to Qeshm International Airport in Iran.
  • E. GSM
    GSM is a classic Onitsuka Tiger sneaker model inspired by vintage tennis shoes, known for its minimalist design and retro athletic style.
  • 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_69e0c479a98081908ce333853fdd4348 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f118e42c108190b6308016655c429e completed April 28, 2026, 8:30 p.m.
Created at: April 16, 2026, 7:03 p.m.