Triple
T12446055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OMA |
E297400
|
entity |
| Predicate | associatedWithICAOCode |
P419
|
FINISHED |
| Object | KOMA |
E297401
|
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: KOMA | Statement: [OMA, associatedWithICAOCode, KOMA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KOMA Context triple: [OMA, associatedWithICAOCode, KOMA]
-
A.
KOMA
chosen
KOMA is the ICAO airport code for Eppley Airfield, the primary commercial airport serving Omaha, Nebraska.
-
B.
Kom
Kom is an ethnic group and kingdom in northwestern Cameroon known for its rich cultural traditions, language, and chieftaincy system.
-
C.
Kress
Kress is a surname most notably associated with Harold F. Kress, an Academy Award–winning American film editor.
-
D.
Leuke Kome
Leuke Kome was an important Nabataean Red Sea port settlement that served as a key hub for trade between Arabia, Egypt, and the Mediterranean world.
-
E.
Tiskre
Tiskre is a residential settlement in northern Estonia, situated near the capital Tallinn and known for its coastal location and suburban character.
- 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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94d90f18c819083a36ff4b9be4a20 |
completed | April 10, 2026, 7:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f63f132d048190b58a8381bdc74cad |
completed | May 2, 2026, 6:14 p.m. |
Created at: April 8, 2026, 9:56 p.m.