Triple
T12023635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Barbara Municipal Airport |
E286218
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | KSBA |
E286219
|
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: KSBA | Statement: [Santa Barbara Municipal Airport, ICAO code, KSBA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KSBA Context triple: [Santa Barbara Municipal Airport, ICAO code, KSBA]
-
A.
KSBA
chosen
KSBA is the ICAO airport code for Santa Barbara Municipal Airport, a public airport serving Santa Barbara, California.
-
B.
KS
KS is the standard two-letter postal abbreviation for the U.S. state of Kansas.
-
C.
KS
KS is the vehicle registration code used on license plates for the German city of Kassel.
-
D.
KSAT
KSAT is the ICAO airport code for San Antonio International Airport, a major commercial airport serving the San Antonio, Texas area.
-
E.
KSBN
KSBN is the ICAO airport code for South Bend International Airport, a commercial and general aviation airport serving South Bend, Indiana, and the surrounding region.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903ee4f9081909e5a58ecbd830b14 |
completed | April 10, 2026, 2:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f48b71e5c48190a58ace8ef7c8928d |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 8, 2026, 9:47 p.m.