Triple
T11092504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAN Hyères |
E262289
|
entity |
| Predicate | hasICAOCode |
P419
|
FINISHED |
| Object | LFTH |
E457582
|
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: LFTH | Statement: [BAN Hyères, hasICAOCode, LFTH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LFTH Context triple: [BAN Hyères, hasICAOCode, LFTH]
-
A.
LFTH
chosen
LFTH is the ICAO airport code for Toulon–Hyères Airport, a regional airport serving the Toulon area in southeastern France.
-
B.
LTFH
LTFH is the ICAO airport code for Samsun-Çarşamba Airport, a public airport serving the city of Samsun in northern Turkey.
-
C.
LF
LF is a German vehicle registration code assigned to the Traunstein district in the state of Bavaria.
-
D.
LF
LF is the commonly used abbreviation for the Linux Foundation, a nonprofit organization that supports and promotes the development of the Linux kernel and other open-source software projects.
-
E.
LFTW
LFTW is the ICAO airport code for Nîmes-Alès-Camargue-Cévennes Airport in southern France.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799ec6564819097624195d0cd9093 |
completed | April 9, 2026, 12:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3e7d3043c8190bdbe0ec51992db0c |
completed | April 18, 2026, 8:21 p.m. |
Created at: April 8, 2026, 9:27 p.m.