Triple
T29407225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GStreamer |
E745802
|
entity |
| Predicate | supportsCustomElements |
P200021
|
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, supportsCustomElements, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCustomElements Context triple: [GStreamer, supportsCustomElements, yes]
-
A.
includesModernElement
Indicates that something contains or incorporates at least one feature, component, or aspect that is characteristic of the modern era.
-
B.
supportsCustomComponentContent
chosen
Indicates that an entity allows or enables the use of user-defined or non-standard components as content within it.
-
C.
hasPolyfills
Indicates that certain functionality is implemented via polyfills to emulate features not natively supported in the target environment.
-
D.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
E.
supportsProp
Indicates that one entity provides assistance, endorsement, or backing for a particular property, attribute, or characteristic of another entity.
- 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.