Triple
T22960028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisville City FC |
E570867
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | LCFC |
—
|
NE NERFINISHED |
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: LCFC | Statement: [Louisville City FC, shortName, LCFC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LCFC Context triple: [Louisville City FC, shortName, LCFC]
-
A.
LCFC
chosen
LCFC is the commonly used abbreviation for Louisville City FC, a professional soccer club based in Louisville, Kentucky.
-
B.
LFC
LFC is the commonly used abbreviation for Linköpings FC, a professional women's football club based in Linköping, Sweden.
-
C.
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.
-
D.
LUFC
LUFC is a common abbreviation for Leeds United Football Club, a professional English football team based in Leeds, West Yorkshire.
-
E.
CUFC
CUFC is the commonly used abbreviation for Colchester United Football Club, an English professional football team based in Colchester, Essex.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f3c96081909abd6ec32103d4c3 |
completed | April 29, 2026, 3:58 a.m. |
Created at: April 17, 2026, 3:47 p.m.