Triple
T4940545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austin Straubel International Airport |
E110919
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | KGRB |
E481459
|
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: KGRB | Statement: [Austin Straubel International Airport, hasCode, KGRB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KGRB Context triple: [Austin Straubel International Airport, hasCode, KGRB]
-
A.
KGRB
chosen
KGRB is the ICAO airport code for Austin Straubel International Airport serving the Green Bay, Wisconsin area.
-
B.
GRB
GRB is the FAA airport code for Green Bay–Austin Straubel International Airport in Green Bay, Wisconsin.
-
C.
KGR
KGR is the Polish vehicle registration code assigned to the Gorlice area in the Lesser Poland Voivodeship.
-
D.
KGN
KGN is the standard three-letter abbreviation used for the Kingston Frontenacs, a major junior ice hockey team in the Ontario Hockey League.
-
E.
KBGR
KBGR is the ICAO airport code for Bangor International Airport, a public airport serving Bangor, Maine, in the United States.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd708a3dcc81908b6628864fe0db0a |
completed | March 20, 2026, 4:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be81c950388190a5a1ed856c4f0830 |
completed | March 21, 2026, 11:32 a.m. |
Created at: March 20, 2026, 1:31 p.m.