Triple
T11803175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francis S. Gabreski Airport |
E280678
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | FOK |
E947237
|
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: FOK | Statement: [Francis S. Gabreski Airport, FAAcode, FOK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FOK Context triple: [Francis S. Gabreski Airport, FAAcode, FOK]
-
A.
FOK
chosen
FOK is the IATA airport code for Francis S. Gabreski Airport, a public and military airfield in Suffolk County, New York.
-
B.
FUK
FUK is the IATA airport code for Fukuoka Airport, a major international and domestic air hub serving the city of Fukuoka in Japan.
-
C.
FRO
FRO is the three-letter ISO 3166-1 alpha-3 country code assigned to the Faroe Islands.
-
D.
FOC
FOC is the IATA airport code for Fuzhou Changle International Airport, the main airport serving Fuzhou in Fujian Province, China.
-
E.
FO
FO is the IATA airline designator assigned to Flybondi, a low-cost carrier based in Argentina.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a5a2048190b68027f622366079 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f166dbcb848190a5942ec00a2ca2f9 |
completed | April 29, 2026, 2:03 a.m. |
Created at: April 8, 2026, 9:42 p.m.