Triple
T12181735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFTP |
E290235
|
entity |
| Predicate | hasICAOCode |
P419
|
FINISHED |
| Object | EFTP |
E290235
|
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: EFTP | Statement: [EFTP, hasICAOCode, EFTP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EFTP Context triple: [EFTP, hasICAOCode, EFTP]
-
A.
EFTP
chosen
EFTP is the ICAO airport code for Pirkkala Air Base, a military and civilian airport serving the Tampere region in Finland.
-
B.
EFD
EFD is the abbreviation for Switzerland’s Federal Department of Finance, the federal ministry responsible for national financial and budgetary policy.
-
C.
EFTI
EFTI is a Swedish film production company known for its involvement in acclaimed Scandinavian cinema, including the horror drama "Let the Right One In."
-
D.
EFS
EFS is a Windows feature that provides built-in file-level encryption to protect data stored on NTFS volumes.
-
E.
EDFE
EDFE is the ICAO airport code for Frankfurt Egelsbach Airport, a general aviation airfield near Frankfurt, Germany.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d915fd8dac8190928059ad2b6bbbf3 |
completed | April 10, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60a88b8748190a6c95e143f370010 |
completed | May 2, 2026, 2:30 p.m. |
Created at: April 8, 2026, 9:50 p.m.