Triple
T13809203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erie International Airport |
E331840
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | ERI |
E1062823
|
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: ERI | Statement: [Erie International Airport, FAAcode, ERI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ERI Context triple: [Erie International Airport, FAAcode, ERI]
-
A.
ERI
ERI is the Earthquake Research Institute of the University of Tokyo, a leading Japanese center for seismology and earthquake-related research.
-
B.
ERI
ERI is the former stock ticker symbol for Eldorado Resorts, a U.S.-based casino and hospitality company that later became part of Caesars Entertainment.
-
C.
ERI
chosen
ERI is the IATA airport code for Erie International Airport, a commercial airport serving Erie, Pennsylvania.
-
D.
ERI@N
ERI@N is an energy research institute at Nanyang Technological University in Singapore that focuses on sustainable energy, smart grids, and related clean technology innovations.
-
E.
ER3
ER3 is the IATA aircraft type code used to designate the Embraer ERJ 135 regional jet.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026eae8481908b8880635e6a9152 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b8dc1ec0819098c4f32eb3991613 |
completed | May 3, 2026, 9:06 p.m. |
Created at: April 9, 2026, 10:12 p.m.