Triple
T2218853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris–Le Bourget Airport |
E48093
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | LFPB |
E48093
|
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: LFPB | Statement: [Paris–Le Bourget Airport, ICAO code, LFPB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LFPB Context triple: [Paris–Le Bourget Airport, ICAO code, LFPB]
-
A.
LFPB
chosen
LFPB is the ICAO airport code for Paris–Le Bourget Airport, a historic airfield near Paris known for business aviation and the Paris Air Show.
-
B.
LBF
LBF is the IATA airport code for North Platte Regional Airport serving North Platte, Nebraska.
-
C.
LDPB
LDPB is a Belarusian political party known as the Liberal Democratic Party of Belarus.
-
D.
LFPG
LFPG is the ICAO airport code for Paris Charles de Gaulle Airport, France’s largest and busiest international air hub.
-
E.
LPFR
LPFR is the ICAO airport code for Faro Airport, the main international gateway to Portugal’s Algarve 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc011d50c8190b1c375cc633f8189 |
completed | March 7, 2026, 6:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae6afc6dd881909dd51d8a18ab4c74 |
completed | March 9, 2026, 6:38 a.m. |
Created at: March 4, 2026, 7:46 p.m.