Triple
T7478800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Wayne Airport |
E176696
|
entity |
| Predicate | hasICAOcode |
P419
|
FINISHED |
| Object | KSNA |
E176697
|
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: KSNA | Statement: [John Wayne Airport, hasICAOcode, KSNA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KSNA Context triple: [John Wayne Airport, hasICAOcode, KSNA]
-
A.
KSNA
chosen
KSNA is the ICAO airport code for John Wayne Airport, a commercial and general aviation airport serving Orange County, California.
-
B.
KSVN
KSVN is the ICAO airport code for Hunter Army Airfield, a U.S. Army military airfield located in Savannah, Georgia.
-
C.
KBNA
KBNA is the ICAO airport code for Nashville International Airport, a major commercial airport serving Nashville, Tennessee.
-
D.
KSYR
KSYR is the ICAO airport code for Syracuse Hancock International Airport, a public airport serving Syracuse, New York.
-
E.
KHSV
KHSV is the ICAO airport code for Huntsville International Airport, a public airport serving the Huntsville, Alabama area in the United States.
- 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f4f13f548190a8cc59165735b30e |
completed | March 27, 2026, 9:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8348e8d108190b77e59e9df336d81 |
completed | March 28, 2026, 8:05 p.m. |
Created at: March 27, 2026, 3:42 p.m.