Triple
T2285987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterloo Regional Airport |
E51392
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | ALO |
E252376
|
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: ALO | Statement: [Waterloo Regional Airport, FAAcode, ALO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ALO Context triple: [Waterloo Regional Airport, FAAcode, ALO]
-
A.
ALO
ALO is the Arab Labor Organization, a specialized Arab League body that promotes labor standards, employment policies, and workers’ rights across Arab countries.
-
B.
ALO
chosen
ALO is the three-letter IATA airport code for Waterloo Regional Airport in Waterloo, Iowa, United States.
-
C.
Al
Al is a common shortened form of given names such as Albert, Alan, or Alexander.
-
D.
AL
AL is the common abbreviation for the American League, one of the two major professional baseball leagues that make up Major League Baseball in the United States and Canada.
-
E.
AL
AL is the official postal abbreviation for the Brazilian state of Alagoas, located in the country's Northeast region.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc24730208190af8a5cf443d334f7 |
completed | March 7, 2026, 6:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae894f9ff881909d1b3a7956d82576 |
completed | March 9, 2026, 8:48 a.m. |
Created at: March 4, 2026, 7:48 p.m.