Triple
T29407223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GStreamer |
E745802
|
entity |
| Predicate | supportsTimeSeeking |
P74590
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [GStreamer, supportsTimeSeeking, yes]
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 (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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 2:54 p.m.