Triple
T13002881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIHA |
E322212
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | FIHA |
E322212
|
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: FIHA | Statement: [FIHA, abbreviation, FIHA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FIHA Context triple: [FIHA, abbreviation, FIHA]
-
A.
FIHA
chosen
FIHA is the commonly used abbreviation for the Finnish Ice Hockey Association, the governing body for ice hockey in Finland.
-
B.
FIH
FIH is the IATA airport code for N’djili International Airport, the main international gateway serving Kinshasa in the Democratic Republic of the Congo.
-
C.
FIF
FIF is the abbreviation for the Fife Flyers, a professional ice hockey team based in Kirkcaldy, Scotland.
-
D.
FAI
FAI is the IATA airport code for Fairbanks International Airport, a major air transport hub serving Fairbanks and interior Alaska.
-
E.
FAI
FAI is an Italian non-profit foundation dedicated to protecting, restoring, and promoting Italy’s cultural, historical, and natural heritage.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9a2a448190968833354280e474 |
completed | April 10, 2026, 10:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6c103e49c8190a140527f24b5c799 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 9, 2026, 8:47 p.m.