Triple
T29181760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TI OMAP3430 |
E739762
|
entity |
| Predicate | hasVideoAcceleration |
P82506
|
FINISHED |
| Object | hardware video encode |
—
|
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: hardware video encode | Statement: [TI OMAP3430, hasVideoAcceleration, hardware video encode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVideoAcceleration Context triple: [TI OMAP3430, hasVideoAcceleration, hardware video encode]
-
A.
supportsHardwareAcceleration
chosen
Indicates that one entity enables or provides hardware-based acceleration capabilities for another entity’s operations or processes.
-
B.
supportsIntelQuickSyncVideo
Indicates that one entity provides compatibility with or functional support for Intel Quick Sync Video hardware-accelerated video processing.
-
C.
hardwareAcceleration
Indicates that an operation or process is executed using specialized hardware resources (such as GPU or dedicated accelerators) rather than relying solely on general-purpose CPU computation.
-
D.
supportsHEVCEncode
Indicates that one entity provides the capability for another entity to perform HEVC (High Efficiency Video Coding) encoding.
-
E.
supportsHEVC
Indicates that one entity provides compatibility with or the ability to handle HEVC (High Efficiency Video Coding) for 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 28, 2026, 11:57 a.m.