Triple

T21569077
Position Surface form Disambiguated ID Type / Status
Subject Rail Express Systems E532237 entity
Predicate abbreviation P43 FINISHED
Object RES 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: RES | Statement: [Rail Express Systems, abbreviation, RES]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RES
Context triple: [Rail Express Systems, abbreviation, RES]
  • A. RES chosen
    RES is the abbreviation for Rail Express Systems, a former British Rail sector that specialized in high-speed mail and parcels services.
  • B. RES
    RES is the IATA airport code for Resistencia International Airport serving the city of Resistencia in Argentina.
  • C. RE
    RE is the common abbreviation for the British Army’s Corps of Royal Engineers, responsible for military engineering and technical support.
  • D. RE
    RE is a centrist, pro-European French political party founded by Emmanuel Macron and formerly known as La République En Marche!.
  • E. RE
    RE is the vehicle registration code used for the city of Recklinghausen in Germany.
  • 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_69e0c460db088190828c64206a450273 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eee9cb9718819094fc95b25df68bd1 completed April 27, 2026, 4:44 a.m.
Created at: April 16, 2026, 6:30 p.m.