Triple
T29509729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chance Liga |
E748613
|
entity |
| Predicate | sponsorshipNaming |
P26420
|
FINISHED |
| Object | named after betting company Chance |
—
|
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: named after betting company Chance | Statement: [Chance Liga, sponsorshipNaming, named after betting company Chance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorshipNaming Context triple: [Chance Liga, sponsorshipNaming, named after betting company Chance]
-
A.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
-
B.
sponsorshipNameAdopted
chosen
Indicates that an entity has adopted or taken on a specific sponsorship name as its official or recognized designation.
-
C.
sponsorshipRenamedFrom
Indicates that a sponsorship currently known by one name previously existed under a different, earlier name.
-
D.
sponsorshipBrand
Indicates that one entity serves as a sponsoring brand for another entity, typically providing support, funding, or endorsement.
-
E.
sponsoredNameHolder
Indicates that one entity holds or uses a name or title under the sponsorship or endorsement of another entity.
- F. None of above.
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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 4:31 p.m.