Triple
T2149309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris–Le Bourget Airport |
E47142
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | LBG |
E48092
|
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: LBG | Statement: [Paris–Le Bourget Airport, IATAcode, LBG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LBG Context triple: [Paris–Le Bourget Airport, IATAcode, LBG]
-
A.
LBG
chosen
LBG is the IATA airport code for Paris–Le Bourget Airport, a historic airfield near Paris known for hosting the Paris Air Show.
-
B.
BLBA
BLBA is a U.S. federal law that provides compensation and medical benefits to coal miners (and their survivors) who are disabled by pneumoconiosis, commonly known as black lung disease.
-
C.
LB
LB is the two-letter ISO 3166-1 alpha-2 country code representing Lebanon.
-
D.
LBF
LBF is the IATA airport code for North Platte Regional Airport serving North Platte, Nebraska.
-
E.
LGB
LGB is the IATA airport code for Long Beach Airport, a public airport serving the Long Beach and greater Los Angeles area in California.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe44d2608190986467d43ee224d4 |
completed | March 7, 2026, 5:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae58dc0b608190b5c6aed5b6b034fd |
completed | March 9, 2026, 5:21 a.m. |
Created at: March 4, 2026, 7:44 p.m.