Triple
T5221494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto FC |
E117878
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | TFC |
E117877
|
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: TFC | Statement: [Toronto FC, shortName, TFC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TFC Context triple: [Toronto FC, shortName, TFC]
-
A.
TFC
chosen
TFC is a professional Major League Soccer club based in Toronto, Ontario, known for its passionate fan base and home matches at BMO Field.
-
B.
TFC
TFC is the common abbreviation for Toulouse FC, a professional football club based in Toulouse, France that competes in Ligue 1.
-
C.
TFC
TFC is the stock ticker symbol for Truist Financial Corporation, a major U.S. bank holding company formed from the merger of BB&T and SunTrust.
-
D.
TFC II
TFC II is a Canadian professional soccer reserve team that serves as the developmental squad for Toronto FC.
-
E.
CLTFC
CLTFC is an abbreviation commonly used for Charlotte FC, the Major League Soccer club based in Charlotte, North Carolina.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7aba05b48190b6a7fc52ab3532f0 |
completed | March 20, 2026, 4:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69befe5e0d4c819095ea8b185754394e |
completed | March 21, 2026, 8:23 p.m. |
Created at: March 20, 2026, 1:48 p.m.