Triple
T8114345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Bahama International Airport |
E189433
|
entity |
| Predicate | pushpinLabel |
P9248
|
FINISHED |
| Object | FPO |
E713184
|
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: FPO | Statement: [Grand Bahama International Airport, pushpinLabel, FPO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FPO Context triple: [Grand Bahama International Airport, pushpinLabel, FPO]
-
A.
FPO
FPO is the commonly used abbreviation for the Orinoco Petroleum Belt, a vast oil-rich region in Venezuela containing some of the world’s largest extra-heavy crude reserves.
-
B.
FPO
chosen
FPO is the IATA airport code for Grand Bahama International Airport, serving Freeport in the Bahamas.
-
C.
FPF
FPF is the Portuguese Football Federation, the national governing body responsible for organizing and overseeing football in Portugal, including its national teams.
-
D.
FRO
FRO is the three-letter ISO 3166-1 alpha-3 country code assigned to the Faroe Islands.
-
E.
FOPA
FOPA is a U.S. federal law enacted in 1986 that revised and expanded regulations on the sale, ownership, and transportation of firearms.
- 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_69ca82baad008190ab2859712b9b1607 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb432f2a24819097be6ab9b03567bd |
completed | March 31, 2026, 3:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ccbea5d39c819099d52545410ae564 |
completed | April 1, 2026, 6:43 a.m. |
Created at: March 30, 2026, 5:32 p.m.