Triple
T18433446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chattanooga Metropolitan Airport |
E450330
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | CHA |
—
|
NE NERFINISHED |
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: CHA | Statement: [Chattanooga Metropolitan Airport, FAAcode, CHA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CHA Context triple: [Chattanooga Metropolitan Airport, FAAcode, CHA]
-
A.
CHA
The Charlotte Hornets are a professional basketball team based in Charlotte, North Carolina, competing in the NBA's Eastern Conference.
-
B.
CHA
CHA is the standard abbreviation used for the Chattanooga Lookouts, a Minor League Baseball team based in Chattanooga, Tennessee.
-
C.
CHA
CHA is the vehicle registration code for the city of Cham in Germany.
-
D.
CHA
CHA is the standard abbreviation used for the Charlottetown Islanders, a major junior ice hockey team in the Quebec Maritimes Junior Hockey League based in Charlottetown, Prince Edward Island.
-
E.
CHA
chosen
CHA is the three-letter IATA airport code for Chattanooga Metropolitan Airport in Chattanooga, Tennessee.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b1915d88190a1ecd81cd78ee7d2 |
completed | April 19, 2026, 6:12 p.m. |
Created at: April 10, 2026, 11:27 a.m.