Triple

T2296223
Position Surface form Disambiguated ID Type / Status
Subject Redmond Municipal Airport E51620 entity
Predicate FAAcode P420 FINISHED
Object RDM E253693 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: RDM | Statement: [Redmond Municipal Airport, FAAcode, RDM]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RDM
Context triple: [Redmond Municipal Airport, FAAcode, RDM]
  • A. RDM chosen
    RDM is the IATA airport code for Redmond Municipal Airport, a commercial airport serving the Bend–Redmond area in central Oregon, USA.
  • B. RM
    RM is the currency symbol that was used to denote the German Reichsmark, the former official currency of Germany from 1924 to 1948.
  • C. RMF
    RMF (Resource Measurement Facility) is an IBM performance monitoring and reporting tool used to analyze and manage system resources on z/OS mainframe environments.
  • D. RdR
    RdR is the abbreviated name of the Council for German Orthography, the official body responsible for regulating and updating German spelling rules.
  • E. RCM
    RCM is a Canadian Earth observation satellite constellation that uses radar imaging to monitor environmental changes, maritime activity, and national security.
  • 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_69a88b0a9f248190bcff941463d8f65a completed March 4, 2026, 7:42 p.m.
NER Named-entity recognition batch_69abc5dc40f881908a3dcc518bbead55 completed March 7, 2026, 6:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae8952322c81909d58b89139f51a27 completed March 9, 2026, 8:48 a.m.
Created at: March 4, 2026, 7:49 p.m.