Triple
T10445592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linköpings FC |
E246277
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | LFC |
E864251
|
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: LFC | Statement: [Linköpings FC, abbreviation, LFC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LFC Context triple: [Linköpings FC, abbreviation, LFC]
-
A.
LFC
LFC is the commonly used abbreviation for Land Forces Command, the army component responsible for overseeing and directing a nation's land-based military operations.
-
B.
LFC
chosen
LFC is the commonly used abbreviation for Linköpings FC, a professional women's football club based in Linköping, Sweden.
-
C.
LUFC
LUFC is a common abbreviation for Leeds United Football Club, a professional English football team based in Leeds, West Yorkshire.
-
D.
Liverpool F.C.
Liverpool F.C. is a globally renowned English football club based in Liverpool, known for its rich history, passionate fanbase, and major domestic and European successes.
-
E.
Chelsea
Chelsea is a small, densely populated city in Massachusetts located just across the Mystic River from downtown Boston.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fdbf81508190a160edea85105d3a |
completed | April 7, 2026, 12:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d89fa5b3b081909af7de1745372add |
completed | April 10, 2026, 6:58 a.m. |
Created at: April 6, 2026, 12:16 p.m.