Triple
T17542652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAFC |
E427239
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SAFC |
—
|
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: SAFC | Statement: [SAFC, abbreviation, SAFC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SAFC Context triple: [SAFC, abbreviation, SAFC]
-
A.
SAFC
chosen
SAFC is the commonly used abbreviation for Stirling Albion Football Club, a Scottish professional football team based in Stirling.
-
B.
SAFC
SAFC is the commonly used abbreviation for San Antonio FC, a professional soccer club based in San Antonio, Texas, that competes in the USL Championship.
-
C.
FAFC
FAFC is the common abbreviation for Forfar Athletic Football Club, a Scottish professional football team based in the town of Forfar.
-
D.
SFC
SFC is the commonly used abbreviation for the Scottish Funding Council, the national body responsible for funding colleges and universities in Scotland.
-
E.
SFC
SFC is the commonly used abbreviation for Southampton Football Club, a professional English football team based in Southampton that competes in the English football league system.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4545f1fa08190870c9244d06cf5f6 |
completed | April 19, 2026, 4:04 a.m. |
Created at: April 10, 2026, 5:49 a.m.