Triple
T19465369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill and Hillary Clinton National Airport |
E486981
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | KLIT |
—
|
NE NERFINISHED |
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: KLIT | Statement: [Bill and Hillary Clinton National Airport, ICAOcode, KLIT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KLIT Context triple: [Bill and Hillary Clinton National Airport, ICAOcode, KLIT]
-
A.
KLIT
chosen
KLIT is the ICAO airport code for Bill and Hillary Clinton National Airport, the primary commercial airport serving Little Rock, Arkansas.
-
B.
KLAL
KLAL is the ICAO airport code for Lakeland Linder International Airport in Lakeland, Florida, a regional airport known for general aviation and cargo operations.
-
C.
KLu
KLu is the commonly used abbreviation for the Royal Netherlands Air Force, the aerial warfare branch of the Dutch armed forces.
-
D.
KL
KL is the two-letter IATA airline code assigned to KLM Royal Dutch Airlines.
-
E.
KL
KL is the abbreviation commonly used for the Royal Netherlands Army, the land forces branch of the Dutch Armed Forces.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633d0fe3c8190b637f78bfad704d0 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 10, 2026, 1:39 p.m.