Triple
T1398425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KSLC |
E30723
|
entity |
| Predicate | hasIATACode |
P2569
|
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: [KSLC, hasIATACode, SLC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SLC Context triple: [KSLC, hasIATACode, 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.
SLC
SLC is a collegiate athletic conference in the NCAA Division I primarily comprising universities from the South Central United States.
-
C.
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.
-
D.
SL1
SL1 is a Boston bus rapid transit route on the MBTA Silver Line that connects downtown with Logan International Airport.
-
E.
SL
SL is the public transport authority and brand responsible for operating and coordinating the mass transit system in the Stockholm region of Sweden.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c382b6588190833c39ac84fb6139 |
completed | March 1, 2026, 10:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acde353b148190b9122f1d6d80fbd4 |
completed | March 8, 2026, 2:25 a.m. |
Created at: March 1, 2026, 7:59 p.m.