Triple
T38099048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sportsnet Now |
E951324
|
entity |
| Predicate | streamsEventType |
P190568
|
FINISHED |
| Object | regular season games |
—
|
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: regular season games | Statement: [Sportsnet Now, streamsEventType, regular season games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streamsEventType Context triple: [Sportsnet Now, streamsEventType, regular season games]
-
A.
streams
Indicates that one entity continuously transmits or delivers data, media, or content in real time to another entity.
-
B.
storesStreamType
Indicates that one entity persistently holds or records information about the type or category of a data stream associated with another entity.
-
C.
streamsSport
Indicates that one entity broadcasts or provides live coverage of a particular sport.
-
D.
meteorStreamType
Indicates the classification or category of a meteor stream based on its physical or observational characteristics.
-
E.
streamingRecord
Indicates that an entity maintains a record or log of streaming activity or streamed content associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:21 p.m.