Triple
T17225812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salina Municipal Airport |
E418110
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | SLN |
E1257551
|
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: SLN | Statement: [Salina Municipal Airport, FAAcode, SLN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SLN Context triple: [Salina Municipal Airport, FAAcode, SLN]
-
A.
SLN
chosen
SLN is the three-letter IATA airport code for Salina Municipal Airport in Salina, Kansas, United States.
-
B.
SL1
SL1 is a Boston bus rapid transit route on the MBTA Silver Line that connects downtown with Logan International Airport.
-
C.
SL
SL is a mid-range trim level designation used by Holden for certain Torana models, offering additional comfort and convenience features over the base variants.
-
D.
SL
SL is the post-nominal abbreviation used in Finland to denote a person who has been awarded a decoration of the Order of the Lion of Finland.
-
E.
SL
The Mercedes-Benz SL is a long-running line of luxury grand touring roadsters renowned for combining high performance with elegant design and advanced technology.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42de1674c81909ca9e87fa9153640 |
completed | April 19, 2026, 1:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0170ed74688190b15ef6d7e0cebe86 |
completed | May 11, 2026, 6:02 a.m. |
Created at: April 10, 2026, 5:38 a.m.