Triple
T17579121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langley Air Force Base |
E428150
|
entity |
| Predicate | hasFAAcode |
P420
|
FINISHED |
| Object | LFI |
—
|
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: LFI | Statement: [Langley Air Force Base, hasFAAcode, LFI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LFI Context triple: [Langley Air Force Base, hasFAAcode, LFI]
-
A.
LFI
chosen
LFI is the IATA airport code for Langley Air Force Base, a United States Air Force installation in Virginia.
-
B.
LFLI
LFLI is the ICAO airport code for Annemasse Aerodrome, a small regional airfield serving the Annemasse area in southeastern France near the Swiss border.
-
C.
LFSB
LFSB is the ICAO airport code for EuroAirport Basel–Mulhouse–Freiburg, the international airport serving the tri-border region of France, Switzerland, and Germany.
-
D.
LFLS
LFLS is the ICAO airport code for Grenoble Alpes–Isère Airport, a regional airport serving the Grenoble area in southeastern France.
-
E.
FLF
FLF is the National Rail station code for Flowery Field railway station in Greater Manchester, England.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463cc493c8190965680cf786aa531 |
completed | April 19, 2026, 5:10 a.m. |
Created at: April 10, 2026, 5:50 a.m.