Triple
T11314988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W. K. Kellogg Airport |
E267942
|
entity |
| Predicate | FAAIdentifier |
P420
|
FINISHED |
| Object | BTL |
E917462
|
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: BTL | Statement: [W. K. Kellogg Airport, FAAIdentifier, BTL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BTL Context triple: [W. K. Kellogg Airport, FAAIdentifier, BTL]
-
A.
BTL
chosen
BTL is the IATA airport code for W. K. Kellogg Airport, a public airport serving the Battle Creek, Michigan area.
-
B.
BT1
BT1 is the central Belfast city centre postcode district in Northern Ireland, covering key commercial and civic areas including Donegall Square.
-
C.
BRL
BRL is the official currency code for the Brazilian real, the legal tender of Brazil.
-
D.
KBTL
KBTL is the ICAO airport code for W. K. Kellogg Airport, a public aviation facility serving the Battle Creek, Michigan area.
-
E.
BLC
BLC is the commonly used abbreviation for the Boston Landmarks Commission, the city agency responsible for identifying and protecting Boston’s historic buildings and districts.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c2c7b081909af8acebc8aa93aa |
completed | April 9, 2026, 6:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e525c35538819085d76f7cdf362316 |
completed | April 19, 2026, 6:58 p.m. |
Created at: April 8, 2026, 9:32 p.m.