Triple

T20856262
Position Surface form Disambiguated ID Type / Status
Subject British Rail Class 220 E513488 entity
Predicate safetySystem P840 FINISHED
Object OTMR 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: OTMR | Statement: [British Rail Class 220, safetySystem, OTMR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: OTMR
Context triple: [British Rail Class 220, safetySystem, OTMR]
  • A. OTMR chosen
    OTMR is an on-train data recording system used on British rail vehicles to log operational and safety-related information for monitoring and incident investigation.
  • B. OMTR
    OMTR was the NASDAQ stock ticker symbol for Omniture, a web analytics and online marketing optimization company later acquired by Adobe.
  • C. OTZ
    OTZ is the IATA airport code for Ralph Wien Memorial Airport, a public airport serving Kotzebue in northwestern Alaska, United States.
  • D. TMR
    TMR is the Queensland Government agency responsible for planning, managing, and regulating the state’s transport systems and major road infrastructure.
  • E. TMO
    TMO is the stock ticker symbol for Thermo Fisher Scientific, a leading global provider of scientific instruments, reagents, and laboratory services.
  • 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_69e0b4f5b01081909452f654d2fc3f50 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c3a81ac4819084a07625b8ed4ec5 completed April 21, 2026, 12:24 a.m.
Created at: April 16, 2026, 12:44 p.m.