Triple
T20757071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EuroAirport Basel–Mulhouse–Freiburg |
E510876
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | LFSB |
—
|
NE NERFINISHED |
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: LFSB | Statement: [EuroAirport Basel–Mulhouse–Freiburg, ICAOCode, LFSB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LFSB Context triple: [EuroAirport Basel–Mulhouse–Freiburg, ICAOCode, LFSB]
-
A.
LFSB
chosen
LFSB is the ICAO airport code for EuroAirport Basel–Mulhouse–Freiburg, the international airport serving the tri-border region of France, Switzerland, and Germany.
-
B.
LFLS
LFLS is the ICAO airport code for Grenoble Alpes–Isère Airport, a regional airport serving the Grenoble area in southeastern France.
-
C.
LFSD
LFSD is the ICAO airport code for Dijon-Bourgogne Airport in Dijon, France.
-
D.
LBF
LBF is the IATA airport code for North Platte Regional Airport serving North Platte, Nebraska.
-
E.
LFPB
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c23113c88190a567c3a098cf7552 |
completed | April 21, 2026, 12:17 a.m. |
Created at: April 16, 2026, 12:35 p.m.