Triple
T22555683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Scott Municipal Airport |
E557674
|
entity |
| Predicate | faaLid |
P420
|
FINISHED |
| Object | FSK |
—
|
NE NERFINISHED |
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: FSK | Statement: [Fort Scott Municipal Airport, faaLid, FSK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FSK Context triple: [Fort Scott Municipal Airport, faaLid, FSK]
-
A.
FSK
FSK is Norway’s premier special operations force, known for conducting high-risk counterterrorism, reconnaissance, and special missions at home and abroad.
-
B.
FSK
chosen
FSK is the IATA airport code for Fort Scott Municipal Airport, a public airport serving Fort Scott, Kansas, United States.
-
C.
FSK
FSK is the National Rail station code assigned to Finstock railway station in Oxfordshire, England.
-
D.
USK
USK is the German Entertainment Software Self-Regulation Body responsible for age rating and classifying video games and other interactive media.
-
E.
CBFC
CBFC is India’s national film certification authority responsible for reviewing and rating movies before public exhibition.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f78d8288190871d54db0a7f454b |
completed | April 29, 2026, 1:31 a.m. |
Created at: April 16, 2026, 8:52 p.m.