Triple
T7548475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunnison–Crested Butte Regional Airport |
E178466
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | GUC |
E671426
|
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: GUC | Statement: [Gunnison–Crested Butte Regional Airport, FAAcode, GUC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GUC Context triple: [Gunnison–Crested Butte Regional Airport, FAAcode, GUC]
-
A.
GUC
chosen
GUC is the IATA airport code for Gunnison–Crested Butte Regional Airport, which serves the Gunnison and Crested Butte area in Colorado, United States.
-
B.
GUF
GUF is the three-letter ISO 3166-1 alpha-3 country code assigned to French Guiana.
-
C.
GU
GU is the two-letter ISO 3166 country code assigned to Guam, an unincorporated territory of the United States in the western Pacific Ocean.
-
D.
GU
GU is a United Kingdom postcode area covering Guildford and surrounding parts of Surrey and nearby counties.
-
E.
UG
UG is the ISO 3166-1 alpha-2 country code for Uganda, used in international standards and country abbreviations.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f89b9afc8190b3e61a8e2cea7ad7 |
completed | March 27, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c856bb83b88190947c0efed84b891a |
completed | March 28, 2026, 10:31 p.m. |
Created at: March 27, 2026, 3:49 p.m.