Triple
T16210851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bastia – Poretta Airport |
E393459
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | BIA |
E393459
|
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: BIA | Statement: [Bastia – Poretta Airport, IATA code, BIA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BIA Context triple: [Bastia – Poretta Airport, IATA code, BIA]
-
A.
BIA
BIA is a U.S. federal agency within the Department of the Interior responsible for managing relations and services for Native American tribes and Alaska Natives.
-
B.
BIA
BIA is the station code used to identify Białystok railway station in Poland’s rail network.
-
C.
BIA
chosen
BIA is the IATA airport code for Bastia – Poretta Airport, the main air gateway serving the city of Bastia on the French island of Corsica.
-
D.
BIA
BIA is a contributor associated with the Safari web browser project.
-
E.
BIA
BIA is the acronym for the Board of Immigration Appeals, the highest administrative body for interpreting and applying U.S. immigration laws.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22713282481909c7c0d0782213461 |
completed | April 17, 2026, 12:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0007932f088190b6c20913cfb932f4 |
completed | May 10, 2026, 4:20 a.m. |
Created at: April 10, 2026, 5:03 a.m.