Triple
T13843077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Bee |
E332715
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | BF |
E65660
|
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: BF | Statement: [French Bee, IATAcode, BF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BF Context triple: [French Bee, IATAcode, BF]
-
A.
BF
chosen
BF is the IATA airline designator for French Bee, a French low-cost long-haul carrier.
-
B.
BF
BF is the two-letter ISO 3166-1 alpha-2 country code assigned to Burkina Faso.
-
C.
Bf
Bf is the aircraft designation prefix historically used for military aircraft designed or built by the German manufacturer Bayerische Flugzeugwerke, notably including early Messerschmitt fighters.
-
D.
BFU
BFU is the commonly used abbreviation for Burgas Free University, a higher education institution located in Burgas, Bulgaria.
-
E.
FA
FA is the governing body of association football in England, responsible for overseeing the national teams, competitions, and the rules of the game within the country.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02afce788190a74dce4e6a3569fa |
completed | April 14, 2026, 9:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b8f87c188190b90faf7678cb9ad4 |
completed | May 3, 2026, 9:07 p.m. |
Created at: April 9, 2026, 10:13 p.m.