Triple
T10188513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florennes Air Base |
E236972
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | EBFS |
E236972
|
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: EBFS | Statement: [Florennes Air Base, ICAOCode, EBFS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EBFS Context triple: [Florennes Air Base, ICAOCode, EBFS]
-
A.
EBFS
chosen
EBFS is the ICAO airport code for Florennes Air Base, a military airfield in Belgium.
-
B.
ESFS
ESFS is the acronym for the European System of Financial Supervision, the EU’s framework of supervisory authorities and bodies that oversee the stability and proper functioning of its financial system.
-
C.
EBFN
EBFN is the ICAO airport code for Koksijde Air Base, a military airfield in Belgium.
-
D.
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.
-
E.
EFS
EFS is a Windows feature that provides built-in file-level encryption to protect data stored on NTFS volumes.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded7c3278819093312665b54d888c |
completed | April 2, 2026, 4:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d317b734a4819085645caea8ba0481 |
completed | April 6, 2026, 2:17 a.m. |
Created at: March 30, 2026, 9:12 p.m.