Triple
T13759548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manassas Regional Airport |
E330566
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | KHEF |
E330565
|
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: KHEF | Statement: [Manassas Regional Airport, ICAO code, KHEF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KHEF Context triple: [Manassas Regional Airport, ICAO code, KHEF]
-
A.
KHEF
chosen
KHEF is the ICAO airport code for Manassas Regional Airport, a public airport serving the Manassas, Virginia area in the United States.
-
B.
HCKE
HCKE is the official abbreviation for HC Košice, a professional ice hockey club based in Košice, Slovakia.
-
C.
KEPH
KEPH is the ICAO airport code for Ephrata Municipal Airport in Ephrata, Washington, United States.
-
D.
HEF
HEF is the German vehicle registration code assigned to the district of Hersfeld-Rotenburg, centered around the town of Bad Hersfeld in Hesse.
-
E.
HEF
HEF is the FAA location identifier for Manassas Regional Airport in Virginia, a public airport serving general aviation and regional air traffic.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0223ab9081909db05334860405e0 |
completed | April 14, 2026, 9 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b06faed88190abc44e6256cb9301 |
completed | May 3, 2026, 8:30 p.m. |
Created at: April 9, 2026, 10:09 p.m.