Triple
T20045942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bally Sports Great Lakes |
E497556
|
entity |
| Predicate | hasStreamingApp |
P80625
|
FINISHED |
| Object | Bally Sports app |
—
|
LITERAL 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: Bally Sports app | Statement: [Bally Sports Great Lakes, hasStreamingApp, Bally Sports app]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreamingApp Context triple: [Bally Sports Great Lakes, hasStreamingApp, Bally Sports app]
-
A.
hasStreaming
Indicates that an entity provides or supports streaming access to another entity (such as media, data, or content).
-
B.
hasStreamingAvailability
chosen
Indicates that a media item is available to be streamed through a particular streaming service or platform.
-
C.
hasStreamingEligibility
Indicates that an entity is qualified or permitted to be made available via a streaming service or platform.
-
D.
supportsStreamingServices
Indicates that one entity provides compatibility or functionality enabling the use of streaming services for another entity.
-
E.
hasOnlineStreamingSuccess
Indicates that an entity has achieved notable popularity, viewership, or impact through online streaming platforms.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632a5e888190ade41657ffd057f6 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.