Triple
T12088312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangor International Airport |
E287868
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | BGR |
E287867
|
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: BGR | Statement: [Bangor International Airport, IATA code, BGR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BGR Context triple: [Bangor International Airport, IATA code, BGR]
-
A.
BGR
BGR is a technology and entertainment news website known for its coverage of consumer electronics, mobile devices, and digital culture.
-
B.
BGR
BGR is the three-letter ISO 3166-1 alpha-3 country code assigned to Bulgaria.
-
C.
BGR
chosen
BGR is the three-letter IATA airport code for Bangor International Airport in Bangor, Maine, United States.
-
D.
BRG
BRG is the stock ticker symbol for Borregaard, a Norwegian company specializing in advanced and sustainable biochemicals derived from wood.
-
E.
RYG
RYG is the IATA airport code for Moss Airport, Rygge, a former civil and military airport in southeastern Norway.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915161f848190a6355c1e372eadaa |
completed | April 10, 2026, 3:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e42cd588190835b3e8160bdbba5 |
completed | May 2, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:48 p.m.