Triple
T6790090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QuickTime |
E155909
|
entity |
| Predicate | supportsProgressiveDownload |
P73008
|
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: [QuickTime, supportsProgressiveDownload, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProgressiveDownload Context triple: [QuickTime, supportsProgressiveDownload, yes]
-
A.
supportsMultipleStreams
Indicates that the subject is capable of handling or maintaining more than one data or communication stream at the same time.
-
B.
supportsCompressedFiles
Indicates that one entity is capable of handling, reading, or working with files that are stored in a compressed format.
-
C.
supportsProResDecode
Indicates that one entity is capable of decoding or otherwise handling ProRes-encoded media for another entity or in a given context.
-
D.
hasStreamingEligibility
Indicates that an entity is qualified or permitted to be made available via a streaming service or platform.
-
E.
supportsHEVCEncode
Indicates that one entity provides the capability for another entity to perform HEVC (High Efficiency Video Coding) encoding.
- F. None of above. chosen
Provenance (4 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2ab4ce88190b6311e4d5aac758c |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1b0d2a48190b249dcc671b9b5e4 |
completed | March 27, 2026, 6:51 p.m. |
Created at: March 27, 2026, 2:15 p.m.