Triple
T10755842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LaGrange–Callaway Airport |
E253690
|
entity |
| Predicate | hasIATACode |
P2569
|
FINISHED |
| Object | LGC |
E253690
|
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: LGC | Statement: [LaGrange–Callaway Airport, hasIATACode, LGC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LGC Context triple: [LaGrange–Callaway Airport, hasIATACode, LGC]
-
A.
LGC
chosen
LGC is the three-letter IATA airport code for LaGrange–Callaway Airport in LaGrange, Georgia, United States.
-
B.
CLGC
CLGC is the abbreviated name for Cavs Legion GC, the Cleveland Cavaliers’ official NBA 2K League esports team.
-
C.
LCG
LCG is the National Rail station code assigned to Lochgelly railway station in Fife, Scotland.
-
D.
DGC
DGC is the United Nations Department of Global Communications, responsible for promoting global awareness and understanding of the UN’s work through strategic communication and public outreach.
-
E.
DGC
DGC is a record label imprint best known for signing influential alternative rock and grunge artists in the late 1980s and 1990s.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d72e9e224c819099d16aba77322812 |
completed | April 9, 2026, 4:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de84a63de0819085f1e982c8348811 |
completed | April 14, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:15 p.m.