Triple
T13093157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super League |
E310513
|
entity |
| Predicate | sponsor |
P67
|
FINISHED |
| Object | Betfred |
E97908
|
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: Betfred | Statement: [Super League, sponsor, Betfred]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Betfred Context triple: [Super League, sponsor, Betfred]
-
A.
Betfred
chosen
Betfred is a major UK-based bookmaker and online gambling company known for its extensive sports betting and gaming operations.
-
B.
Betfair
Betfair is a major online gambling company and betting exchange based in the United Kingdom.
-
C.
Afabet
Afabet is a town in Eritrea known historically as a key site during the Eritrean War of Independence.
-
D.
BetRivers
BetRivers is an online sports betting and casino brand operated by Rush Street Interactive and linked to the Rivers Casino properties in the United States.
-
E.
Betclic
Betclic is a European online sports betting and gambling company known for sponsoring major professional sports leagues and events.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813cd1b881909871a318fdd60672 |
completed | April 10, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d617f1908190a2fa147bedede54f |
completed | May 3, 2026, 4:59 a.m. |
Created at: April 9, 2026, 9:03 p.m.