Triple
T5616402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakeland Linder International Airport |
E147487
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | LAL |
E537097
|
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: LAL | Statement: [Lakeland Linder International Airport, FAAcode, LAL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LAL Context triple: [Lakeland Linder International Airport, FAAcode, LAL]
-
A.
LAL
LAL is the standard NBA abbreviation for the Los Angeles Lakers basketball franchise.
-
B.
LAL
chosen
LAL is the IATA airport code for Lakeland Linder International Airport, a public airport serving Lakeland, Florida.
-
C.
LAA
LAA is the standard Major League Baseball abbreviation for the Los Angeles Angels franchise.
-
D.
Lala
Lala is an Indian honorific title traditionally used as a respectful prefix for educated or distinguished men, particularly in North India.
-
E.
LAJ
LAJ is the station code for La Junta station, an Amtrak railroad stop in La Junta, Colorado, serving long-distance passenger trains.
- 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c021da7f848190bb1cd0270ad6398f |
completed | March 22, 2026, 5:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c05a0ab9cc8190a01c5309e6cfc598 |
completed | March 22, 2026, 9:07 p.m. |
Created at: March 22, 2026, 3:39 p.m.