Triple
T10684497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sioux Falls Regional Airport |
E251840
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | FSD |
E251840
|
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: FSD | Statement: [Sioux Falls Regional Airport, FAA LID, FSD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FSD Context triple: [Sioux Falls Regional Airport, FAA LID, FSD]
-
A.
FSD
chosen
FSD is the IATA airport code for Sioux Falls Regional Airport, the primary commercial airport serving Sioux Falls, South Dakota.
-
B.
FSP
FSP is the station code used to identify Schweizer Platz station in the Frankfurt public transport network.
-
C.
FSR
FSR is AMD's open-source spatial upscaling technology designed to boost gaming performance and image quality across a wide range of GPUs.
-
D.
FSR
FSR is a periodic publication by central banks or financial authorities that assesses risks and vulnerabilities in the financial system to support economic stability and policy decisions.
-
E.
FDS
FDS is the onboard computer system on NASA’s Voyager 1 spacecraft responsible for managing instruments and formatting data for transmission back to Earth.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc5134c8190bcb1d96a32634c17 |
completed | April 9, 2026, 1:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dbb6fa3f54819081910a2589ddbc99 |
completed | April 12, 2026, 3:15 p.m. |
Created at: April 8, 2026, 9:10 p.m.