Triple
T21552812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schaumburg Regional Airport |
E531808
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | K06C |
—
|
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: K06C | Statement: [Schaumburg Regional Airport, ICAOCode, K06C]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: K06C Context triple: [Schaumburg Regional Airport, ICAOCode, K06C]
-
A.
K06C
chosen
K06C is the ICAO airport code assigned to Schaumburg Regional Airport in Illinois, United States.
-
B.
K06A
K06A is the ICAO airport code for Moton Field Municipal Airport in Tuskegee, Alabama, historically associated with the Tuskegee Airmen.
-
C.
K-61
K-61 is a north–south state highway in central Kansas that connects the Hutchinson area with McPherson and the U.S. Highway network.
-
D.
K-66
K-66 is a short state highway in southeastern Kansas that follows a former alignment of historic U.S. Route 66.
-
E.
K-635
K-635 is a short Kansas state highway that serves as the Kansas segment of Interstate 635, connecting I-35 and I-70 in the Kansas City metropolitan area.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb594956c8190a5b4d81911e3927d |
completed | April 27, 2026, 1:02 a.m. |
Created at: April 16, 2026, 6:29 p.m.