Triple
T14420913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GameStream |
E357579
|
entity |
| Predicate | streamSource |
P409
|
FINISHED |
| Object | user-owned gaming PC |
—
|
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: user-owned gaming PC | Statement: [GameStream, streamSource, user-owned gaming PC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streamSource Context triple: [GameStream, streamSource, user-owned gaming PC]
-
A.
streams
Indicates that one entity continuously transmits or delivers data, media, or content in real time to another entity.
-
B.
headstreamOf
Indicates that one watercourse is the primary upstream source or originating branch of another watercourse.
-
C.
samplingSource
Indicates that one entity serves as the origin or provider from which another entity is sampled or drawn.
-
D.
streamingRecord
Indicates that an entity maintains a record or log of streaming activity or streamed content associated with another entity.
-
E.
source
chosen
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
- 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.