Triple
T14761673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 07/25 |
E346875
|
entity |
| Predicate | IATAAirportCode |
P418
|
FINISHED |
| Object | DEN |
E259069
|
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: DEN | Statement: [Runway 07/25, IATAAirportCode, DEN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DEN Context triple: [Runway 07/25, IATAAirportCode, DEN]
-
A.
DEN
chosen
DEN is the three-letter IATA airport code for Denver International Airport, the primary commercial airport serving Denver, Colorado.
-
B.
DN
DN is the official vehicle registration code used for the Indian union territory of Dadra and Nagar Haveli and Daman and Diu.
-
C.
DN
DN is a UK postcode area covering Doncaster and surrounding parts of South Yorkshire and Lincolnshire, including North East Lincolnshire.
-
D.
Den
Den is a Japanese surname borne by various notable figures in politics, industry, and the arts.
-
E.
Den
Den is a central fictional character from the British soap opera "EastEnders," known for his complex relationships and dramatic storylines in the early years of the show.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7f207dc819088a53f717736a121 |
completed | April 14, 2026, 11:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0cf24c0081909221cb7d761e882f |
completed | May 8, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:30 a.m.