Triple
T10820523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missoula Montana Airport |
E255356
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | MSO |
E449363
|
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: MSO | Statement: [Missoula Montana Airport, IATACode, MSO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MSO Context triple: [Missoula Montana Airport, IATACode, MSO]
-
A.
MSO
chosen
MSO is the National Rail station code for Moston railway station in Greater Manchester, England.
-
B.
MOSB
MOSB is an abbreviation for the Military Order of the Stars and Bars, a heritage organization composed primarily of descendants of Confederate officers and officials.
-
C.
MSS
MSS is the Mobile Servicing System, a Canadian-built robotic arm and handling system used on the International Space Station for assembly, maintenance, and payload operations.
-
D.
MSH
MSH is the vehicle registration code for the Mansfeld-Südharz district in the German state of Saxony-Anhalt.
-
E.
MSA
MSA is the standardized, literary form of Arabic used in formal writing, media, education, and official communication across the Arab world.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d73449eee88190afa52c4e6ef96baa |
completed | April 9, 2026, 5:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de8569178481909474e939a3e4c217 |
completed | April 14, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:18 p.m.