Triple
T14420902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GameStream |
E357579
|
entity |
| Predicate | streamingDirection |
P99702
|
FINISHED |
| Object | from PC to client device |
—
|
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: from PC to client device | Statement: [GameStream, streamingDirection, from PC to client device]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streamingDirection Context triple: [GameStream, streamingDirection, from PC to client device]
-
A.
streamingStatus
Indicates the current state or condition of an ongoing or potential media stream, such as whether it is active, paused, stopped, or unavailable.
-
B.
streamingRecord
Indicates that an entity maintains a record or log of streaming activity or streamed content associated with another entity.
-
C.
streamedOnline
Indicates that an event, performance, or content was broadcast live or made available in real time over the internet.
-
D.
feedDirection
chosen
Indicates the direction or orientation in which material, energy, or information is supplied or fed from one entity to another.
-
E.
hasStreamingAvailability
Indicates that a media item is available to be streamed through a particular streaming service or platform.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de910eb354819089d5d5a46919eb49 |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.