Triple
T16210881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bastia – Poretta Airport |
E393460
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | LFKB |
E393460
|
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: LFKB | Statement: [Bastia – Poretta Airport, ICAO code, LFKB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LFKB Context triple: [Bastia – Poretta Airport, ICAO code, LFKB]
-
A.
LFKB
chosen
LFKB is the ICAO airport code for Bastia – Poretta Airport, a commercial airport serving the city of Bastia on the French island of Corsica.
-
B.
LFKF
LFKF is the ICAO airport code for Figari–Sud Corse Airport, a regional airport serving the southern part of Corsica, France.
-
C.
FKB
FKB is the IATA airport code for Karlsruhe/Baden-Baden Airport in southwestern Germany.
-
D.
LFBL
LFBL is the ICAO airport code for Limoges – Bellegarde Airport, a regional airport serving the city of Limoges in west-central France.
-
E.
LFKC
LFKC is the ICAO airport code for Calvi – Sainte-Catherine Airport, a regional airport serving the town of Calvi on the French island of Corsica.
- 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_6a000ed13b40819096de333872225730 |
completed | May 10, 2026, 4:51 a.m. |
Created at: April 10, 2026, 5:03 a.m.