Triple
T14204812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannibal Regional Airport |
E352060
|
entity |
| Predicate | faaLid |
P420
|
FINISHED |
| Object | HAE |
E1085571
|
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: HAE | Statement: [Hannibal Regional Airport, faaLid, HAE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HAE Context triple: [Hannibal Regional Airport, faaLid, HAE]
-
A.
HAE
chosen
HAE is the IATA airport code for Hannibal Regional Airport, a public airport serving the Hannibal, Missouri area in the United States.
-
B.
HAA
HAA is the Harvard Alumni Association, the organization that connects and serves Harvard University’s global community of alumni.
-
C.
HFA
HFA is the commonly used acronym for the New York State Housing Finance Agency, a public authority that finances affordable housing developments across New York State.
-
D.
HFA
HFA is the IATA airport code for Haifa Airport, a regional airport serving the city of Haifa in northern Israel.
-
E.
AHA
AHA is the commonly used acronym for Atlantic Hockey, a collegiate ice hockey conference in the NCAA.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61f6d4d481909128084e82e6a58a |
completed | April 14, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd280c948c8190948e55f1e1874f69 |
completed | May 8, 2026, 12:02 a.m. |
Created at: April 10, 2026, 1:05 a.m.