Triple
T29407200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GStreamer |
E745802
|
entity |
| Predicate | supportsClockSynchronization |
P5737
|
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, supportsClockSynchronization, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsClockSynchronization Context triple: [GStreamer, supportsClockSynchronization, yes]
-
A.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
B.
hasClock
chosen
Indicates that one entity possesses, contains, or is equipped with a clock.
-
C.
synchronizationType
Indicates the specific manner or mode in which two or more processes, systems, or events are coordinated to operate in temporal or state alignment.
-
D.
bitSynchronizationSupport
Indicates whether a system, device, or protocol provides mechanisms to align and maintain timing at the bit level between communicating entities.
-
E.
synchronizesWith
Indicates that two or more entities coordinate their states or activities so that they occur in step or remain temporally consistent with each other.
- 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.