Triple
T12940911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hobart Airport |
E309633
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | HBA |
E309633
|
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: HBA | Statement: [Hobart Airport, IATA code, HBA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HBA Context triple: [Hobart Airport, IATA code, HBA]
-
A.
HBA
chosen
HBA is the IATA airport code for Hobart Airport, the main airport serving Hobart in Tasmania, Australia.
-
B.
HAA
HAA is the Harvard Alumni Association, the organization that connects and serves Harvard University’s global community of alumni.
-
C.
BHB
BHB is the stock exchange of the Kingdom of Bahrain, providing a regulated marketplace for trading securities and other financial instruments.
-
D.
HAB
HAB is the HIV/AIDS Bureau, a U.S. federal agency component that oversees programs and funding to improve care and treatment for people living with HIV.
-
E.
HHB
HHB is the National Rail station code for Heysham Port railway station in Lancashire, 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97dca2ee88190b45fafe7d53c35c9 |
completed | April 10, 2026, 10:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6af70f45c8190a40250da4a787d8f |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 9, 2026, 5:43 p.m.