Triple
T10912333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cincinnati Municipal Lunken Airport |
E257731
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | LUK |
E894156
|
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: LUK | Statement: [Cincinnati Municipal Lunken Airport, FAAcode, LUK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LUK Context triple: [Cincinnati Municipal Lunken Airport, FAAcode, LUK]
-
A.
LUK
chosen
LUK is the three-letter IATA airport code for Cincinnati Municipal Lunken Airport, a public airport serving the Cincinnati, Ohio area.
-
B.
Luki
Luki is a common diminutive or nickname for the given name Lukas.
-
C.
Lukin
Lukin is a component or module associated with the "No Code" system, likely serving as a distinct functional part within that broader platform.
-
D.
Lakki
Lakki is a coastal town and main port on the Greek island of Leros in the Dodecanese.
-
E.
LK
LK is the two-letter ISO 3166-1 alpha-2 country code assigned to Sri Lanka for international standardization and identification purposes.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770723df08190bedfdc94d998f969 |
completed | April 9, 2026, 9:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e23baecb008190b74bcbad1db61a91 |
completed | April 17, 2026, 1:54 p.m. |
Created at: April 8, 2026, 9:22 p.m.