Triple
T29407223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GStreamer |
E745802
|
entity |
| Predicate | supportsTimeSeeking |
—
|
GENERATED |
| Object | yes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTimeSeeking Context triple: [GStreamer, supportsTimeSeeking, yes]
-
A.
supportsTimecodes
Indicates that one entity can handle, interpret, or work with timecode information associated with another entity or data stream.
-
B.
canSeek
Indicates that an entity has the ability or permission to pursue, search for, or attempt to obtain another entity or goal.
-
C.
supportsSeekableStreams
chosen
Indicates that an entity is capable of handling streams that allow seeking to arbitrary positions within the data.
-
D.
supportsTimescale
Indicates that one entity is capable of operating with, accommodating, or being compatible with a specified timescale or range of temporal resolutions.
-
E.
supportsStreamingIn
Indicates that one entity provides or enables streaming functionality within a specified context, environment, or medium.
- F. None of above.
Provenance (1 batch)
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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:54 p.m.