Triple

T6489751
Position Surface form Disambiguated ID Type / Status
Subject Wiley Post–Will Rogers Memorial Airport E148004 entity
Predicate hasCode P9567 FINISHED
Object BRW E596711 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: BRW | Statement: [Wiley Post–Will Rogers Memorial Airport, hasCode, BRW]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: BRW
Context triple: [Wiley Post–Will Rogers Memorial Airport, hasCode, BRW]
  • A. BRW chosen
    BRW is the IATA airport code for Wiley Post–Will Rogers Memorial Airport in Utqiaġvik, Alaska, a key air transport hub for the Arctic region.
  • B. BRD
    BRD is the IATA airport code for Brainerd Lakes Regional Airport, a public airport serving the Brainerd area in Minnesota, United States.
  • C. BR2
    BR2 is a UK postcode district covering parts of Hayes and surrounding areas in the London Borough of Bromley in southeast England.
  • D. BRN
    BRN is the IATA airport code for Bern Airport, the primary airport serving Switzerland’s capital city.
  • E. BR
    BR is the upper house of Austria’s parliament, representing the federal states in the legislative process.
  • 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_69c009088f3081909cd467b05919de30 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c06a9926fc81909db0f390e385e97d completed March 22, 2026, 10:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c66385943081908630aa0f2cdefa06 completed March 27, 2026, 11:01 a.m.
Created at: March 22, 2026, 4:52 p.m.