Triple
T21683063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Carlos de Bariloche Airport |
E535159
|
entity |
| Predicate | hasCityCode |
P6089
|
FINISHED |
| Object | BRC |
—
|
NE NERFINISHED |
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, hasCityCode, BRC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BRC Context triple: [San Carlos de Bariloche Airport, hasCityCode, 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.
BRC
BRC is the station code for Branchton railway station, a local rail stop in Scotland’s Inverclyde area.
-
D.
BRC
BRC is the vehicle registration code used for the city of Brčko in Bosnia and Herzegovina.
-
E.
BRC
BRC is an abbreviation commonly used to refer to a Board Risk Committee, the governing body responsible for overseeing an organization’s risk management framework and policies.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96c7c6a08190bbd9a89b8a3b921b |
completed | April 27, 2026, 5:03 p.m. |
Created at: April 16, 2026, 6:43 p.m.