Triple
T5176095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 1L/19R |
E116801
|
entity |
| Predicate | hasICAOAirport |
P419
|
FINISHED |
| Object | KIAD |
E2980
|
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: KIAD | Statement: [Runway 1L/19R, hasICAOAirport, KIAD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KIAD Context triple: [Runway 1L/19R, hasICAOAirport, KIAD]
-
A.
KIAD
chosen
KIAD is the ICAO airport code for Washington Dulles International Airport, a major international air travel hub serving the Washington, D.C. metropolitan area.
-
B.
KAL
KAL is the ICAO airline designator used to identify Korean Air in international aviation operations.
-
C.
Kindai
Kindai is a major private university in Japan known for its comprehensive academic programs and strong research in fields such as science, engineering, and fisheries.
-
D.
KIX
KIX is the three-letter IATA airport code for Kansai International Airport serving the Osaka region of Japan.
-
E.
KIWA
KIWA is the ICAO airport code for Phoenix–Mesa Gateway Airport, a commercial and general aviation airport serving the Phoenix metropolitan area in Arizona, United States.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd797349008190b87ad9d0d3eb667f |
completed | March 20, 2026, 4:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bed94e269481908118fd1af1fc6a44 |
completed | March 21, 2026, 5:45 p.m. |
Created at: March 20, 2026, 1:45 p.m.