Triple
T10328578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TransformStream |
E242821
|
entity |
| Predicate | supportsPiping |
P28421
|
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: [TransformStream, supportsPiping, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPiping Context triple: [TransformStream, supportsPiping, true]
-
A.
supportsMultipleStreams
Indicates that the subject is capable of handling or maintaining more than one data or communication stream at the same time.
-
B.
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.
-
C.
supportsProgressiveDownload
Indicates that an entity enables or is compatible with progressive download, allowing data to be consumed while it is still being transferred.
-
D.
supportsChannels
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
-
E.
pipeline
chosen
Indicates a sequential process or workflow where the output of one stage is passed as input to the next to achieve a final result.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cf21e08190bf605daeea0d9dcf |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:52 a.m.