Triple
T9055471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuma International Airport |
E216984
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | YUM |
E718379
|
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: YUM | Statement: [Yuma International Airport, IATAcode, YUM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: YUM Context triple: [Yuma International Airport, IATAcode, YUM]
-
A.
YUM
YUM is a command-line package management utility for RPM-based Linux distributions that automatically handles software installation, updates, and dependency resolution.
-
B.
YUM
YUM is the stock ticker symbol for Yum! Brands, the multinational fast-food corporation that owns KFC, Taco Bell, and Pizza Hut.
-
C.
YUM
chosen
YUM is the IATA airport code for Marine Corps Air Station Yuma, a joint-use military and civilian airfield in Yuma, Arizona.
-
D.
RPM
RPM is a widely used package management system originally developed for Linux distributions to build, install, and manage software packages.
-
E.
YAM
YAM is the IATA airport code for Sault Ste. Marie Airport in Ontario, Canada.
- 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_69ca83d4425481909a319dab847724ec |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7a7488188190b3dd6bc2f2377503 |
completed | April 1, 2026, 1:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfebdb01a8819084365c9b73506a28 |
completed | April 3, 2026, 4:33 p.m. |
Created at: March 30, 2026, 7:10 p.m.