Triple
T17671683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KBNA |
E440534
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | BNA |
—
|
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: BNA | Statement: [KBNA, IATACode, BNA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BNA Context triple: [KBNA, IATACode, BNA]
-
A.
BNA
BNA is the vehicle registration code assigned to motor vehicles registered in the district of Leipzig in Germany.
-
B.
BNA
BNA is the central bank of Angola, responsible for issuing the national currency and overseeing the country’s monetary and financial stability.
-
C.
BNA
BNA is the abbreviation commonly used for the Bulgarian People's Army, the former armed forces of the People's Republic of Bulgaria during the socialist era.
-
D.
BNA
chosen
BNA is the three-letter IATA airport code for Nashville International Airport, the primary commercial airport serving Nashville, Tennessee.
-
E.
BNA Kubus
BNA Kubus is a prestigious Dutch architecture award presented by the Royal Institute of Dutch Architects (BNA) to recognize outstanding contributions to the field of architecture.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f69b11c8190b09add33f81776b3 |
completed | April 19, 2026, 6 a.m. |
Created at: April 10, 2026, 9:59 a.m.