Triple
T20336048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bally Sports Detroit |
E492612
|
entity |
| Predicate | producesProgrammingType |
P2192
|
FINISHED |
| Object | live game broadcasts |
—
|
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: live game broadcasts | Statement: [Bally Sports Detroit, producesProgrammingType, live game broadcasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producesProgrammingType Context triple: [Bally Sports Detroit, producesProgrammingType, live game broadcasts]
-
A.
producedProgram
Indicates that one entity created or produced a specific program (such as a TV show, software, or other structured content).
-
B.
programType
chosen
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
C.
programGeneration
Indicates that one entity creates, writes, or produces a program (such as software or code) for or on behalf of another entity.
-
D.
madeProgram
Indicates that one entity created, developed, or authored a program (such as software or a coded application).
-
E.
programBasedOn
Indicates that one program is derived from, inspired by, or constructed using the content, structure, or principles of another program or source.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677eb4d5881908ea5ec5a1dd7eafa |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:23 a.m.