Triple
T28961624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obtener un sí |
E731912
|
entity |
| Predicate | isOnStreamingServices |
P127597
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Obtener un sí, isOnStreamingServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnStreamingServices Context triple: [Obtener un sí, isOnStreamingServices, yes]
-
A.
supportsStreamingServices
Indicates that one entity provides compatibility or functionality enabling the use of streaming services for another entity.
-
B.
streamingService
Indicates that one entity provides or delivers media content over the internet to another entity in real time or on demand.
-
C.
isPopularOnStreamingPlatforms
chosen
Indicates that an entity enjoys significant attention, usage, or viewership across one or more streaming platforms.
-
D.
streamedOnline
Indicates that an event, performance, or content was broadcast live or made available in real time over the internet.
-
E.
sisterStreamingService
Indicates that one streaming service is a closely related or affiliated counterpart to another, typically under the same ownership or network group.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65c292f488190844784ea28afd91c |
completed | May 2, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:50 a.m.