Triple
T11326225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itami Airport |
E268225
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | ITM |
E40875
|
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: ITM | Statement: [Itami Airport, IATAcode, ITM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ITM Context triple: [Itami Airport, IATAcode, ITM]
-
A.
ITM
chosen
ITM is the IATA airport code for Osaka International Airport, a major domestic airport serving the Osaka metropolitan area in Japan.
-
B.
IMTS
IMTS is one of the world’s largest trade shows for manufacturing technology, showcasing advanced machine tools, automation, and related innovations.
-
C.
ITI
ITI is a leading U.S.-based trade association that represents major global technology companies and advocates for public policies on innovation, cybersecurity, and the digital economy.
-
D.
IMT-SC
IMT-SC is a CDMA-based terrestrial radio interface standard within the IMT-2000 family designed to support third-generation mobile communication services.
-
E.
IMT-FT
IMT-FT is a radio interface standard within the IMT-2000 family, developed to provide third-generation (3G) mobile communication services.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e2253881909518cad0f12ef612 |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e52608b7348190875597513ca1a995 |
completed | April 19, 2026, 6:59 p.m. |
Created at: April 8, 2026, 9:32 p.m.