Triple
T10181545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawthorne Municipal Airport |
E236796
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | HHR |
E845747
|
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: HHR | Statement: [Hawthorne Municipal Airport, FAAcode, HHR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HHR Context triple: [Hawthorne Municipal Airport, FAAcode, HHR]
-
A.
HHR
chosen
HHR is the IATA airport code for Hawthorne Municipal Airport, a public airport serving the city of Hawthorne in Los Angeles County, California.
-
B.
H4H
H4H is a U.S. federal mortgage relief initiative designed to help struggling homeowners refinance into more affordable, government-insured loans.
-
C.
HARV
HARV is the standard abbreviation used for the Harvard Crimson men's basketball team in collegiate athletics contexts.
-
D.
HOR
HOR is the IATA airport code for Horta Airport, which serves the island of Faial in Portugal’s Azores archipelago.
-
E.
HOR
HOR is the National Rail station code for Horley railway station in Surrey, England.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded32b91c8190b01ad37b2456080a |
completed | April 2, 2026, 4:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d31792490c819088c89444f75cdbc9 |
completed | April 6, 2026, 2:16 a.m. |
Created at: March 30, 2026, 9:12 p.m.