Triple
T7239172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Antonio FC |
E155309
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | SAFC |
E650814
|
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: SAFC | Statement: [San Antonio FC, hasAbbreviation, SAFC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SAFC Context triple: [San Antonio FC, hasAbbreviation, SAFC]
-
A.
SAFC
SAFC is the commonly used abbreviation for Stirling Albion Football Club, a Scottish professional football team based in Stirling.
-
B.
SAFC
chosen
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.
SFA
The SFA is the Scottish Football Association, the main governing body for football in Scotland.
-
E.
SFA
SFA is the IATA airport code for Sfax–Thyna International Airport serving the city of Sfax in Tunisia.
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea37fa9081908e9c3abe49d151e5 |
completed | March 27, 2026, 8:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7d38efa4c8190abd6434188d8c58f |
completed | March 28, 2026, 1:11 p.m. |
Created at: March 27, 2026, 2:55 p.m.