Triple
T3832832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falkirk F.C. |
E91053
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | FFC |
E91053
|
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: FFC | Statement: [Falkirk F.C., abbreviation, FFC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FFC Context triple: [Falkirk F.C., abbreviation, FFC]
-
A.
FFC
chosen
FFC is the commonly used abbreviation for Falkirk Football Club, a professional Scottish football team based in Falkirk.
-
B.
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.
-
C.
FFA
FFA is the commonly used abbreviation for the Fédération Française d’Athlétisme, the governing body for athletics in France.
-
D.
FFD
FFD is the IATA airport code for RAF Fairford, a Royal Air Force station in Gloucestershire, England, used by both the UK and United States air forces and known for hosting major airshows.
-
E.
FFS
FFS is the commonly used abbreviation for the Swiss Federal Railways, the national railway company of Switzerland.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb88b8a8819082d4bdbc5bc45366 |
completed | March 9, 2026, 3:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b512259d048190be25add7e38a0326 |
completed | March 14, 2026, 7:45 a.m. |
Created at: March 9, 2026, 3:17 p.m.