Triple
T4368501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillsboro Airport |
E98836
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | HIO |
E433835
|
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: HIO | Statement: [Hillsboro Airport, FAAcode, HIO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HIO Context triple: [Hillsboro Airport, FAAcode, HIO]
-
A.
HIO
chosen
HIO is the IATA airport code for Hillsboro Airport, a public aviation facility serving the Hillsboro area in Oregon, United States.
-
B.
TIOH
TIOH is the commonly used acronym for the United States Army Institute of Heraldry, the organization responsible for designing and overseeing official military symbols, insignia, and heraldic items for the U.S. Army and other federal agencies.
-
C.
HIH
HIH is an honorific abbreviation used to refer to a female member of an imperial family bearing the style "Her Imperial Highness."
-
D.
Hiyo
Hiyo was a Japanese aircraft carrier of the Imperial Japanese Navy that served during World War II.
-
E.
HIG
HIG is the stock ticker symbol for The Hartford Financial Services Group, a major U.S.-based insurance and investment company.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352034d3881909ed4b2f9eef5e823 |
completed | March 12, 2026, 11:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5e50838188190b5b698d4bd2b5784 |
completed | March 14, 2026, 10:45 p.m. |
Created at: March 12, 2026, 11:17 p.m.