Triple
T9640580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadym Airport |
E233053
|
entity |
| Predicate | hasIATACode |
P2569
|
FINISHED |
| Object | NYM |
E33965
|
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: NYM | Statement: [Nadym Airport, hasIATACode, NYM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NYM Context triple: [Nadym Airport, hasIATACode, NYM]
-
A.
NYM
chosen
NYM is the standard abbreviation used for the New York Mets, a Major League Baseball team based in New York City.
-
B.
NYN
NYN is the former stock ticker symbol for NYNEX Corporation, a regional Bell operating telephone company that later became part of Verizon Communications.
-
C.
NYP
NYP is the abbreviation for the New York Philharmonic, one of the oldest and most renowned symphony orchestras in the United States.
-
D.
NYL
NYL is the FAA location identifier for Yuma International Airport in Yuma, Arizona.
-
E.
NYNH&H
NYNH&H was a major railroad company in the northeastern United States that operated extensive passenger and freight services across New York, Connecticut, Rhode Island, and Massachusetts in the late 19th and early 20th centuries.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b552a1c81909a1fab347110eeb1 |
completed | April 1, 2026, 10:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18248ffe4819095d4ea20951eca01 |
completed | April 4, 2026, 9:27 p.m. |
Created at: March 30, 2026, 8:12 p.m.