Triple
T35804799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony Ten |
E1035074
|
entity |
| Predicate | streamsOn |
P3189
|
FINISHED |
| Object | SonyLIV |
—
|
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: SonyLIV | Statement: [Sony Ten, streamsOn, SonyLIV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streamsOn Context triple: [Sony Ten, streamsOn, SonyLIV]
-
A.
streamingSeries
Indicates that one entity is a serialized media work (such as a TV or web series) that is available to be watched via a streaming platform or service.
-
B.
streamedOnline
Indicates that an event, performance, or content was broadcast live or made available in real time over the internet.
-
C.
streamingService
chosen
Indicates that one entity provides or delivers media content over the internet to another entity in real time or on demand.
-
D.
streamingCategory
Indicates the classification or genre under which a piece of content is organized or presented on a streaming platform.
-
E.
streamingStatus
Indicates the current state or condition of an ongoing or potential media stream, such as whether it is active, paused, stopped, or unavailable.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.