Triple
T13088986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGNM |
E310409
|
entity |
| Predicate | hasIATAcode |
P2569
|
FINISHED |
| Object | LBA |
E281501
|
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: LBA | Statement: [EGNM, hasIATAcode, LBA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LBA Context triple: [EGNM, hasIATAcode, LBA]
-
A.
LBA
chosen
LBA is the IATA airport code for Leeds Bradford Airport, a regional international airport serving the cities of Leeds and Bradford in West Yorkshire, England.
-
B.
LBA
LBA is the acronym for the Logistics Base of the Armed Forces, the central organization responsible for providing and coordinating logistical support to a nation's military.
-
C.
LBA
LBA is the German Federal Aviation Office responsible for civil aviation oversight, safety regulation, and certification in Germany.
-
D.
LAP
LAP is the ICAO airline designator used to identify LATAM Airlines Paraguay in international aviation operations.
-
E.
LBU
LBU is the IATA airport code for Labuan Airport, which serves the island of Labuan in Malaysia.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d98138a1d481908a139f2f67eb3472 |
completed | April 10, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d614704481908758cf8691a941ea |
completed | May 3, 2026, 4:59 a.m. |
Created at: April 9, 2026, 9:02 p.m.