Triple
T23025569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 14L/32R |
E573299
|
entity |
| Predicate | hasICAOAirportCode |
P419
|
FINISHED |
| Object | LFBO |
—
|
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: LFBO | Statement: [Runway 14L/32R, hasICAOAirportCode, LFBO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LFBO Context triple: [Runway 14L/32R, hasICAOAirportCode, LFBO]
-
A.
LFBO
chosen
LFBO is the ICAO airport code for Toulouse-Blagnac Airport, a major international airport serving Toulouse in southwestern France and an important hub for the aerospace industry.
-
B.
LBF
LBF is the IATA airport code for North Platte Regional Airport serving North Platte, Nebraska.
-
C.
LFOB
LFOB is the ICAO airport code for Beauvais–Tillé Airport, a regional international airport serving the Beauvais area near Paris, France.
-
D.
LFBL
LFBL is the ICAO airport code for Limoges – Bellegarde Airport, a regional airport serving the city of Limoges in west-central France.
-
E.
LFPO
LFPO is the ICAO airport code for Paris Orly Airport, a major international airport serving the Paris metropolitan area in France.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1847c671c8190a8095051d8c3cf93 |
completed | April 29, 2026, 4:09 a.m. |
Created at: April 17, 2026, 3:52 p.m.