Triple

T6758277
Position Surface form Disambiguated ID Type / Status
Subject Olympia Regional Airport E154519 entity
Predicate FAAcode P420 FINISHED
Object OLM E617953 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: OLM | Statement: [Olympia Regional Airport, FAAcode, OLM]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: OLM
Context triple: [Olympia Regional Airport, FAAcode, OLM]
  • A. OLM chosen
    OLM is the three-letter IATA airport code for Olympia Regional Airport in Washington State, USA.
  • B. OLEM
    OLEM is a division of the U.S. Environmental Protection Agency responsible for overseeing land preservation, hazardous waste management, and emergency environmental response activities.
  • C. OLMS
    OLMS is a U.S. Department of Labor agency responsible for promoting transparency, democracy, and financial integrity in labor unions and labor-management relations.
  • D. OOL
    OOL is the IATA airport code for Gold Coast Airport, a major domestic and international gateway serving Queensland’s Gold Coast region in Australia.
  • E. OLY
    OLY is the commonly used abbreviation for Olympiacos FC, a major Greek football club based in Piraeus.
  • 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_69c6880fd5808190be684854081e27dd completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d1f90b6c8190b4a17a23aa9ba0fb completed March 27, 2026, 6:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69c71a78feb8819084314c2ae043d289 completed March 28, 2026, 12:02 a.m.
Created at: March 27, 2026, 2:11 p.m.