Triple
T5639145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Carlos de Bariloche Airport |
E124221
|
entity |
| Predicate | hasIATACode |
P2569
|
FINISHED |
| Object | BRC |
E124221
|
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: BRC | Statement: [San Carlos de Bariloche Airport, hasIATACode, BRC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BRC Context triple: [San Carlos de Bariloche Airport, hasIATACode, BRC]
-
A.
BRC
BRC is the commonly used abbreviation for Black Rock City, the temporary city built annually in Nevada’s Black Rock Desert for the Burning Man festival.
-
B.
BRC
chosen
BRC is the IATA airport code for San Carlos de Bariloche’s main international airport in Argentina.
-
C.
BLC
BLC is the commonly used abbreviation for the Boston Landmarks Commission, the city agency responsible for identifying and protecting Boston’s historic buildings and districts.
-
D.
BRL
BRL is the official currency code for the Brazilian real, the legal tender of Brazil.
-
E.
BCS
BCS is the abbreviation for the Bowl Championship Series, the former system used to determine matchups and the national champion in top-tier U.S. college football.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c02283bb248190b29ac6255c78c5ec |
completed | March 22, 2026, 5:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c04d7456408190962c476f2848927e |
completed | March 22, 2026, 8:13 p.m. |
Created at: March 22, 2026, 3:41 p.m.