Triple
T6670516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billings Logan International Airport |
E151715
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | BIL |
E610281
|
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: BIL | Statement: [Billings Logan International Airport, FAAcode, BIL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BIL Context triple: [Billings Logan International Airport, FAAcode, BIL]
-
A.
BIL
chosen
BIL is the three-letter IATA airport code for Billings Logan International Airport in Billings, Montana, United States.
-
B.
BL
BL is the vehicle registration code used on license plates for the Swiss canton of Basel-Landschaft.
-
C.
BL
BL is the postcode area in the United Kingdom that covers Bolton and surrounding parts of Greater Manchester and Lancashire.
-
D.
BL
BL is the two-letter ISO 3166-1 alpha-2 country code assigned to the Caribbean island territory of Saint Barthélemy.
-
E.
BL
BL is the vehicle registration code used on license plates for vehicles registered in the Bratislava Region of Slovakia.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6b0c9163c8190ad959172a8458619 |
completed | March 27, 2026, 4:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6f79f1718819098d8a6d08bf7f919 |
completed | March 27, 2026, 9:33 p.m. |
Created at: March 27, 2026, 2:03 p.m.