Triple
T9829646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps Air Station Miramar |
E238748
|
entity |
| Predicate | hasIATACode |
P2569
|
FINISHED |
| Object | NKX |
E238749
|
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: NKX | Statement: [Marine Corps Air Station Miramar, hasIATACode, NKX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NKX Context triple: [Marine Corps Air Station Miramar, hasIATACode, NKX]
-
A.
NKX
chosen
NKX is the IATA airport code for Marine Corps Air Station Miramar, a major United States Marine Corps aviation facility in San Diego, California.
-
B.
NK
NK is the station code for Nashik Road railway station, a major rail hub serving the city of Nashik in Maharashtra, India.
-
C.
NK
NK is the two-letter IATA airline designator assigned to Spirit Airlines, a U.S.-based ultra-low-cost carrier.
-
D.
NK
NK is the vehicle registration code used on license plates for the Neunkirchen district in Germany.
-
E.
NKo
NKo is a Unicode block that encodes the characters of the N’Ko script used for writing several West African Mande languages.
- 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3282a2481908913addf2b3fa58b |
completed | April 2, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1cc8ca2808190a1da0641162f12d1 |
completed | April 5, 2026, 2:44 a.m. |
Created at: March 30, 2026, 8:32 p.m.