Triple

T18020590
Position Surface form Disambiguated ID Type / Status
Subject Barra Airport E431106 entity
Predicate hasIATAcode P2569 FINISHED
Object BRR E431106 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: BRR | Statement: [Barra Airport, hasIATAcode, BRR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: BRR
Context triple: [Barra Airport, hasIATAcode, BRR]
  • A. BRR chosen
    BRR is the IATA airport code for Barra Airport in Scotland’s Outer Hebrides, famous for its unique tidal beach runway used by scheduled flights.
  • B. BRRIO
    BRRIO is the UN/LOCODE identifier for the Port of Rio de Janeiro, a major Brazilian seaport on the Atlantic coast.
  • C. R.Br.
    R.Br. is the standard botanical author abbreviation for Robert Brown, a pioneering Scottish botanist known for his work on plant taxonomy and the discovery of Brownian motion.
  • D. Br
    Br is the currency symbol used to denote the Ethiopian birr, the official monetary unit of Ethiopia.
  • E. BUR
    BUR is the commonly used abbreviation for the Burnaby Lakers, a Canadian box lacrosse team based in Burnaby, British Columbia.
  • 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_69d8b904530081908bf341d842464856 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4b9c1c5f88190a059ce4f86f7ed36 completed April 19, 2026, 11:17 a.m.
NED1 Entity disambiguation (via context triple) batch_6a034328fef08190a3f78f8bee859d24 completed May 12, 2026, 3:11 p.m.
Created at: April 10, 2026, 10:24 a.m.