Triple

T16807337
Position Surface form Disambiguated ID Type / Status
Subject Fukuoka Airport E408512 entity
Predicate ICAO code P419 FINISHED
Object RJFF E408513 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: RJFF | Statement: [Fukuoka Airport, ICAO code, RJFF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RJFF
Context triple: [Fukuoka Airport, ICAO code, RJFF]
  • A. RJFF chosen
    RJFF is the ICAO airport code for Fukuoka Airport, a major international and domestic aviation hub on Japan’s Kyushu island.
  • B. RJFR
    RJFR is the ICAO airport code for Tsuiki Air Base, a Japan Air Self-Defense Force installation in Fukuoka Prefecture, Japan.
  • C. RJFO
    RJFO is the ICAO airport code assigned to Ōita Airport in Ōita Prefecture, Japan.
  • D. RJFN
    RJFN is the ICAO airport code for Nyutabaru Air Base, a Japan Air Self-Defense Force installation in Miyazaki Prefecture, Japan.
  • E. RJBB
    RJBB is the ICAO airport code for Kansai International Airport, a major international hub built on an artificial island in Osaka Bay, Japan.
  • 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_69d88393905081908d00a86b99996ac8 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b2cd1e8c8190a7a05ba255f711c7 completed April 18, 2026, 4:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00b28f125481909664363904f4c031 completed May 10, 2026, 4:30 p.m.
Created at: April 10, 2026, 5:22 a.m.