Triple

T9876563
Position Surface form Disambiguated ID Type / Status
Subject Brno–Tuřany Airport E240085 entity
Predicate hasCode P9567 FINISHED
Object BRQ E826510 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: BRQ | Statement: [Brno–Tuřany Airport, hasCode, BRQ]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: BRQ
Context triple: [Brno–Tuřany Airport, hasCode, BRQ]
  • A. BRQ chosen
    BRQ is the IATA airport code for Brno–Tuřany Airport, the main international airport serving the city of Brno in the Czech Republic.
  • 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. Br
    Br is the currency symbol used to denote the Ethiopian birr, the official monetary unit of Ethiopia.
  • D. BRA
    BRA is the three-letter ISO 3166-1 alpha-3 country code that uniquely identifies Brazil in international standards and data systems.
  • E. BRW
    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.
  • 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_69ca84e8a0788190b9061811d50fd554 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb3fb58d481908407898912c4b4e9 completed April 2, 2026, 12:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1eae5a31c81908085f637fbbff6d2 completed April 5, 2026, 4:53 a.m.
Created at: March 30, 2026, 8:37 p.m.