Triple

T3609913
Position Surface form Disambiguated ID Type / Status
Subject Cleveland Hopkins International Airport E76460 entity
Predicate FAAcode P420 FINISHED
Object CLE E373934 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: CLE | Statement: [Cleveland Hopkins International Airport, FAAcode, CLE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CLE
Context triple: [Cleveland Hopkins International Airport, FAAcode, CLE]
  • A. CLE
    CLE is the standard abbreviation used for the Cleveland Monsters, a professional ice hockey team in the American Hockey League.
  • B. CLE chosen
    CLE is the three-letter IATA airport code for Cleveland Hopkins International Airport, the primary commercial airport serving the Cleveland, Ohio metropolitan area.
  • C. CL
    CL is the ticker symbol for West Texas Intermediate (WTI) crude oil futures contracts traded on the New York Mercantile Exchange (NYMEX).
  • D. CL
    CL is the common abbreviation for Japan’s professional baseball Central League.
  • E. CE
    CE is the standard abbreviation for the Catholic Encyclopedia, a comprehensive reference work on Catholic doctrine, history, and practice.
  • 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_69ad85da0ba481908b3b48c69efe2b98 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc22b824c8190a85b36185d4957bb completed March 8, 2026, 6:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69b44f02b3c081909705e05ac923f840 completed March 13, 2026, 5:53 p.m.
Created at: March 8, 2026, 3:23 p.m.