Triple
T20079592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Lauderdale Executive Airport |
E499962
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | FXE |
—
|
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: FXE | Statement: [Fort Lauderdale Executive Airport, FAAcode, FXE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FXE Context triple: [Fort Lauderdale Executive Airport, FAAcode, FXE]
-
A.
FXE
chosen
FXE is the IATA airport code for Fort Lauderdale Executive Airport, a busy general aviation and corporate jet airport in Fort Lauderdale, Florida.
-
B.
FX2
FX2 is a 1991 action-thriller film and sequel to the movie "F/X," starring Brian Dennehy and Bryan Brown as they again use movie special-effects skills to outwit criminals.
-
C.
FXMM
FXMM is the ICAO airport code assigned to Moshoeshoe I International Airport in Lesotho.
-
D.
FX
FX is an American cable television network known for airing edgy, critically acclaimed original series and dramas.
-
E.
FX
FX is the identifying squadron code historically used by No. 92 Squadron of the Royal Air Force.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643f93208190ae2a413f88ea9aed |
completed | April 20, 2026, 5:37 p.m. |
Created at: April 11, 2026, 3:40 p.m.