Triple
T8393377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Forks International Airport |
E197995
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | GFK |
E730948
|
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: GFK | Statement: [Grand Forks International Airport, FAAcode, GFK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GFK Context triple: [Grand Forks International Airport, FAAcode, GFK]
-
A.
GFK
GFK is a Turkish professional football club based in Gaziantep that competes in the country's top leagues.
-
B.
GFK
chosen
GFK is the IATA airport code for Grand Forks International Airport, a commercial and general aviation airport serving Grand Forks, North Dakota, USA.
-
C.
FCB
FCB is the abbreviation commonly used for the Cuban Baseball Federation, the governing body for organized baseball in Cuba.
-
D.
FFK
FFK is the football association responsible for organizing and overseeing the national football activities and competitions in Curaçao.
-
E.
GFA
GFA is the ICAO airline designator used for Gulf Air, the national carrier of Bahrain.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8184788081909e9857afff629985 |
completed | March 31, 2026, 8:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce02d5e0648190b33011c2ddca4ad3 |
completed | April 2, 2026, 5:47 a.m. |
Created at: March 30, 2026, 6:03 p.m.