Triple
T5241524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Topeka Regional Airport |
E118352
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | FOE |
E505042
|
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: FOE | Statement: [Topeka Regional Airport, FAA LID, FOE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FOE Context triple: [Topeka Regional Airport, FAA LID, FOE]
-
A.
FOE
chosen
FOE is the IATA airport code for Topeka Regional Airport in Topeka, Kansas, United States.
-
B.
Foe
Foe is a psychological science fiction novel by Iain Reid that explores themes of identity, isolation, and reality within a tense, intimate marriage.
-
C.
F.O.D.
F.O.D. is a fast-paced punk rock track by Green Day, featured as one of the closing songs on their breakthrough 1994 album *Dookie*.
-
D.
Foege
Foege is the surname of William H. Foege, an American epidemiologist renowned for his pivotal role in the global eradication of smallpox.
-
E.
FiO
FiO is the commonly used abbreviation for Frontiers in Optics, a major annual conference focused on advances in optical science and engineering.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b2c50508190b84bab216c30cbfe |
completed | March 20, 2026, 4:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69befe65e3048190899a6316dc4c89eb |
completed | March 21, 2026, 8:24 p.m. |
Created at: March 20, 2026, 1:49 p.m.