Triple
T6073023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic City International Airport |
E135330
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | ACY |
E565933
|
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: ACY | Statement: [Atlantic City International Airport, FAAcode, ACY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ACY Context triple: [Atlantic City International Airport, FAAcode, ACY]
-
A.
ACY
chosen
ACY is the three-letter IATA airport code for Atlantic City International Airport in New Jersey, USA.
-
B.
ACE
ACE (Altamont Corridor Express) is a commuter rail service in California’s San Joaquin Valley and East Bay that provides weekday trains between Stockton and San Jose.
-
C.
ACE
ACE is the commonly used acronym for Arts Council England, the national body that supports and funds arts and culture across England.
-
D.
ACE
ACE is the IATA airport code for Lanzarote Airport in Spain’s Canary Islands.
-
E.
ACE
ACE is a Canadian satellite mission focused on studying Earth's atmosphere and climate through detailed measurements of atmospheric chemistry.
- 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05759d29481908912015e734ab943 |
completed | March 22, 2026, 8:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c125274e1c8190b452fdeeb788a6f2 |
completed | March 23, 2026, 11:33 a.m. |
Created at: March 22, 2026, 4:11 p.m.