Triple
T15058920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strasbourg Airport |
E379569
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | LFST |
E379570
|
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: LFST | Statement: [Strasbourg Airport, hasCode, LFST]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LFST Context triple: [Strasbourg Airport, hasCode, LFST]
-
A.
LFST
chosen
LFST is the ICAO airport code for Strasbourg Airport, an international airport serving the city of Strasbourg in northeastern France.
-
B.
LFSL
LFSL is the ICAO airport code assigned to Brive–Souillac Airport in France.
-
C.
LPST
LPST is the ICAO airport code for Air Base No. 1 in Sintra, a Portuguese Air Force installation near Lisbon, Portugal.
-
D.
FST
FST is the three-letter National Rail station code for London’s Fenchurch Street railway station, a central terminus serving commuter routes in the east of England.
-
E.
FST
FST is a professional regional theatre company in Sarasota, Florida, known for its contemporary plays, cabaret performances, and new play development.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedee50afc8190bf7b0f4bbe8c60a3 |
completed | April 15, 2026, 12:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feae0fd7dc8190a10c8eb7542c3088 |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 3:01 a.m.