Triple
T11262867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plattsburgh International Airport |
E266608
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | PBG |
E914867
|
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: PBG | Statement: [Plattsburgh International Airport, FAA LID, PBG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PBG Context triple: [Plattsburgh International Airport, FAA LID, PBG]
-
A.
PBG
chosen
PBG is the three-letter IATA airport code for Plattsburgh International Airport in Plattsburgh, New York.
-
B.
PBD
PBD is the IATA airport code for Porbandar Airport, a domestic airport serving the city of Porbandar in the Indian state of Gujarat.
-
C.
POG
POG is the IATA airport code for the main airport serving Port-Gentil, a coastal city in Gabon.
-
D.
PFG
PFG is the stock ticker symbol for Principal Financial Group, a U.S.-based global financial services and investment management company.
-
E.
PBB
PBB (Provider Backbone Bridges) is an IEEE networking standard that extends Ethernet to large-scale carrier and service provider networks by encapsulating customer traffic within a provider backbone.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94c066c8190be1e032eb328e5fe |
completed | April 9, 2026, 6 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4f410cb508190bb0ceab51075eec5 |
completed | April 19, 2026, 3:26 p.m. |
Created at: April 8, 2026, 9:31 p.m.