Triple
T19364003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dundee United F.C. |
E484353
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | DUFC |
—
|
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: DUFC | Statement: [Dundee United F.C., shortName, DUFC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DUFC Context triple: [Dundee United F.C., shortName, DUFC]
-
A.
DUFC
chosen
DUFC is the commonly used abbreviation for Dundee United Football Club, a professional football team based in Dundee, Scotland.
-
B.
DUCET
DUCET is the Default Unicode Collation Element Table, a standard reference used to define the sorting and comparison order of Unicode characters across different languages and scripts.
-
C.
DRFC
DRFC is the commonly used abbreviation for Doncaster Rovers Football Club, an English professional football team based in Doncaster, South Yorkshire.
-
D.
FAFC
FAFC is the common abbreviation for Forfar Athletic Football Club, a Scottish professional football team based in the town of Forfar.
-
E.
DCFC
DCFC is a professional soccer club based in Detroit, Michigan, known for its passionate fan base and strong community focus.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619a9ac68819082cf9deadf526156 |
completed | April 20, 2026, 12:18 p.m. |
Created at: April 10, 2026, 1:34 p.m.