Triple
T10900278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luton Airport Parkway railway station |
E257419
|
entity |
| Predicate | stationCode |
P1289
|
FINISHED |
| Object | LTN |
E530090
|
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: LTN | Statement: [Luton Airport Parkway railway station, stationCode, LTN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LTN Context triple: [Luton Airport Parkway railway station, stationCode, LTN]
-
A.
LTN
chosen
LTN is the IATA airport code for London Luton Airport, a major international airport serving the London metropolitan area in the United Kingdom.
-
B.
LT
LT is a mid-level trim designation commonly used by Chevrolet to denote a better-equipped, more comfort- and feature-focused version of its vehicles.
-
C.
LT
LT is the abbreviated name for the Logic Theorist, an early computer program that pioneered automated theorem proving in mathematical logic.
-
D.
Lt
Lt is the standard military abbreviation for the commissioned officer rank of Lieutenant in the Australian Army.
-
E.
LTAN
LTAN is the ICAO airport code assigned to Konya Airport in Konya, Turkey.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d761a2f02881908b70be6499dd8d98 |
completed | April 9, 2026, 8:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e155306e9081909433522eeecf2b7d |
completed | April 16, 2026, 9:31 p.m. |
Created at: April 8, 2026, 9:22 p.m.