Triple

T15441796
Position Surface form Disambiguated ID Type / Status
Subject Batagay Airport E369920 entity
Predicate IATACode P418 FINISHED
Object BQJ E369920 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: BQJ | Statement: [Batagay Airport, IATACode, BQJ]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: BQJ
Context triple: [Batagay Airport, IATACode, BQJ]
  • A. BQJ chosen
    BQJ is the IATA airport code for Batagay Airport serving the settlement of Batagay in Russia’s Sakha Republic.
  • B. BQK
    BQK is the IATA airport code for Brunswick Golden Isles Airport, a regional airport serving Brunswick and the Golden Isles area of coastal Georgia, USA.
  • C. BQH
    BQH is the IATA airport code for London Biggin Hill Airport, a regional airport in southeast London primarily serving general and business aviation.
  • D. BQ
    BQ is the ISO 3166-1 alpha-2 country code assigned to the Caribbean Netherlands, a special municipality grouping of the Netherlands in the Caribbean.
  • E. BQU
    BQU is the IATA airport code for J. F. Mitchell Airport, a small regional airport serving Bequia in Saint Vincent and the Grenadines.
  • 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_69d85a19180081909925012fbf4e62a3 completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ef55f5c8190a32b1b6ad1daf454 completed April 16, 2026, 1:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff2cf7ce7c8190810ef35b6e37254d completed May 9, 2026, 12:47 p.m.
Created at: April 10, 2026, 3:21 a.m.