Triple
T16120678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flair Airlines |
E391127
|
entity |
| Predicate | callsign |
P1565
|
FINISHED |
| Object | FLAIR |
E391127
|
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: FLAIR | Statement: [Flair Airlines, callsign, FLAIR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FLAIR Context triple: [Flair Airlines, callsign, FLAIR]
-
A.
FLAIR
chosen
FLAIR is the radio callsign used by Flair Airlines, a Canadian ultra-low-cost carrier operating domestic and international flights.
-
B.
FLAR
FLAR is a regional financial organization that provides balance-of-payments support, reserve pooling, and financial stability assistance to its Latin American member countries.
-
C.
Flou
Flou is an Italian furniture company renowned for its high-quality designer beds and bedroom furnishings.
-
D.
FLR
FLR is the IATA airport code for Florence Airport, the main international airport serving Florence, Italy.
-
E.
Flair
Flair is a popular line of felt-tip pens known for their smooth writing and vibrant ink, produced under the Paper Mate brand.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20200acac8190a47e6a917ff8dd34 |
completed | April 17, 2026, 9:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff79ecea0819083aa5cb676d49f64 |
completed | May 10, 2026, 3:12 a.m. |
Created at: April 10, 2026, 5 a.m.