Triple
T9371267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln Airport |
E225534
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | LNK |
E794854
|
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: LNK | Statement: [Lincoln Airport, FAAcode, LNK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LNK Context triple: [Lincoln Airport, FAAcode, LNK]
-
A.
LNK
chosen
LNK is the three-letter IATA airport code for Lincoln Airport in Lincoln, Nebraska, USA.
-
B.
KLNK
KLNK is the ICAO airport code for Lincoln Airport, a public airfield serving Lincoln, Nebraska, in the United States.
-
C.
Linky
Linky is a French smart electricity meter system deployed nationwide to enable remote readings, real-time consumption monitoring, and improved grid management.
-
D.
LN1
LN1 is the first French high-speed rail line (LGV Sud-Est), connecting Paris to Lyon and pioneering the TGV network.
-
E.
VNLK
VNLK is the ICAO airport code for Tenzing-Hillary Airport, the small but famous high-altitude airfield serving Lukla in Nepal’s Everest 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5083cbb8819088e8cef26be1b380 |
completed | April 1, 2026, 5:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d100d68d28819082f366f3b5493cfb |
completed | April 4, 2026, 12:15 p.m. |
Created at: March 30, 2026, 7:43 p.m.