Triple
T885194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Love Field |
E19113
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | KDAL |
E104263
|
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: KDAL | Statement: [Dallas Love Field, hasCode, KDAL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KDAL Context triple: [Dallas Love Field, hasCode, KDAL]
-
A.
KDAL
chosen
KDAL is the ICAO airport code for Dallas Love Field, a major airport serving the Dallas, Texas area.
-
B.
KADW
KADW is the ICAO airport code for Joint Base Andrews, a major U.S. military airfield near Washington, D.C.
-
C.
DAK
DAK is the abbreviation for the German Afrika Korps, the German expeditionary force that fought in North Africa during World War II under commanders such as Erwin Rommel.
-
D.
KIAD
KIAD is the ICAO airport code for Washington Dulles International Airport, a major international air travel hub serving the Washington, D.C. metropolitan area.
-
E.
KORD
KORD is the ICAO airport code for Chicago O'Hare International Airport, one of the busiest and most significant air transport hubs in the 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ace5e15c81908cc2e648c9cd52f2 |
completed | March 1, 2026, 9:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7c01f00f48190b954db4a0cb5baa8 |
completed | March 4, 2026, 5:16 a.m. |
Created at: March 1, 2026, 7:39 p.m.