Triple
T8815673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federashon Futbòl Kòrsou |
E209769
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | FFK |
E209772
|
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: FFK | Statement: [Federashon Futbòl Kòrsou, shortName, FFK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FFK Context triple: [Federashon Futbòl Kòrsou, shortName, FFK]
-
A.
FFK
chosen
FFK is the football association responsible for organizing and overseeing the national football activities and competitions in Curaçao.
-
B.
FKK
FKK is the National Rail station code assigned to Falkirk High railway station in Scotland.
-
C.
FFC
FFC is the commonly used abbreviation for Falkirk Football Club, a professional Scottish football team based in Falkirk.
-
D.
FFC
FFC is the common abbreviation for Fluminense Football Club, a traditional Brazilian sports club best known for its professional football team based in Rio de Janeiro.
-
E.
FFA
FFA is the commonly used abbreviation for the Fédération Française d’Athlétisme, the governing body for athletics in 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff2ff248190bafcafe8b3860e53 |
completed | March 31, 2026, 11:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf6fb898388190b96242ff41599250 |
completed | April 3, 2026, 7:43 a.m. |
Created at: March 30, 2026, 6:45 p.m.