Triple
T16853056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | webOS |
E409720
|
entity |
| Predicate | supportsStreamingServices |
P125227
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [webOS, supportsStreamingServices, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStreamingServices Context triple: [webOS, supportsStreamingServices, true]
-
A.
streamingService
Indicates that one entity provides or delivers media content over the internet to another entity in real time or on demand.
-
B.
hasStreamingEligibility
Indicates that an entity is qualified or permitted to be made available via a streaming service or platform.
-
C.
sisterStreamingService
Indicates that one streaming service is a closely related or affiliated counterpart to another, typically under the same ownership or network group.
-
D.
hasStreamingAvailability
Indicates that a media item is available to be streamed through a particular streaming service or platform.
-
E.
hasStreamingServiceBrandExtension
Indicates that a brand has extended into offering a streaming service under its name or umbrella.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37abadc81909d02d329403497d6 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:24 a.m.