Triple
T9025906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple October 2016 Mac event |
E216046
|
entity |
| Predicate | streamedOnline |
P85921
|
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: [Apple October 2016 Mac event, streamedOnline, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streamedOnline Context triple: [Apple October 2016 Mac event, streamedOnline, yes]
-
A.
hasOnlineStreamingSuccess
Indicates that an entity has achieved notable popularity, viewership, or impact through online streaming platforms.
-
B.
streamingService
Indicates that one entity provides or delivers media content over the internet to another entity in real time or on demand.
-
C.
hasStreamingAvailability
Indicates that a media item is available to be streamed through a particular streaming service or platform.
-
D.
streamingReleaseDate
Indicates the date on which a work (such as a film, show, or album) becomes available to the public via a streaming platform.
-
E.
hasStreamingEligibility
Indicates that an entity is qualified or permitted to be made available via a streaming service or platform.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7ce71c81908041814dc9ec1713 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7:07 p.m.