Triple
T33433687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TextEncoderStream |
E856193
|
entity |
| Predicate | supportsStreamingBackpressure |
P93395
|
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: [TextEncoderStream, supportsStreamingBackpressure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStreamingBackpressure Context triple: [TextEncoderStream, supportsStreamingBackpressure, true]
-
A.
supportsBackpressure
chosen
Indicates that the entity can handle and regulate backpressure, allowing it to slow or adjust data flow in response to downstream demand or capacity.
-
B.
supportsStreamingIn
Indicates that one entity provides or enables streaming functionality within a specified context, environment, or medium.
-
C.
hasStreaming
Indicates that an entity provides or supports streaming access to another entity (such as media, data, or content).
-
D.
supportsMultipleStreams
Indicates that the subject is capable of handling or maintaining more than one data or communication stream at the same time.
-
E.
supportsStreamingWithoutDownload
Indicates that one entity enables another to access or play content via streaming in real time without requiring the content to be downloaded first.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:36 a.m.