Triple
T238261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt Lake City International Airport |
E4871
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | SLC |
E30722
|
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: SLC | Statement: [Salt Lake City International Airport, FAAcode, SLC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SLC Context triple: [Salt Lake City International Airport, FAAcode, SLC]
-
A.
SLC
chosen
SLC is the three-letter IATA airport code for Salt Lake City International Airport, a major air travel hub serving Salt Lake City, Utah.
-
B.
SLD
SLD was a particle physics experiment at the SLAC Linear Collider that made precision measurements of electroweak interactions, including properties of the Z boson.
-
C.
SLV
SLV is the three-letter ISO 3166-1 alpha-3 country code assigned to El Salvador.
-
D.
LAS
LAS is the commonly used abbreviation for the Arab League, a regional organization of Arab countries in and around North Africa, the Horn of Africa, and the Middle East.
-
E.
KSLC
KSLC is the ICAO airport code for Salt Lake City International Airport, a major air transportation hub serving Salt Lake City, Utah.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25ccda0ac8190a44f4bebfc0aba67 |
completed | Feb. 28, 2026, 3:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3695ec8cc8190a070462cd0022f6a |
completed | Feb. 28, 2026, 10:17 p.m. |
Created at: Feb. 28, 2026, 2:53 a.m.