Triple
T3850520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Gatwick Airport |
E85283
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | LGW |
E85283
|
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: LGW | Statement: [London Gatwick Airport, IATACode, LGW]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LGW Context triple: [London Gatwick Airport, IATACode, LGW]
-
A.
LGW
chosen
LGW is the three-letter IATA airport code for London Gatwick Airport, a major international airport serving the London metropolitan area in the United Kingdom.
-
B.
WLG
WLG is the three-letter IATA airport code assigned to Wellington Airport, the main international gateway to New Zealand’s capital city.
-
C.
LWL
LWL is the vehicle registration code assigned to the Włodawa area in eastern Poland.
-
D.
LW
LW is the station code used to identify Lawrence West station on Toronto's subway system.
-
E.
ALWEG
ALWEG was a German transportation company best known for pioneering the modern straddle-beam monorail system that inspired several iconic monorail installations worldwide.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebcf67788190975105131baabc4b |
completed | March 9, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b504172d58819089d19f5cb7b803ec |
completed | March 14, 2026, 6:45 a.m. |
Created at: March 9, 2026, 3:19 p.m.