Triple
T32377575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Pentium Gold 4415Y |
E827330
|
entity |
| Predicate | supportsClearVideoHD |
P201866
|
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: [Intel Pentium Gold 4415Y, supportsClearVideoHD, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsClearVideoHD Context triple: [Intel Pentium Gold 4415Y, supportsClearVideoHD, yes]
-
A.
supportsIntelClearVideoHD
chosen
Indicates that one entity provides compatibility with or functional support for Intel Clear Video HD technology used for enhanced video playback and processing.
-
B.
supportsVideoPlayback
Indicates that an entity is capable of playing or rendering video content.
-
C.
supportsMinimumVideoConfiguration
Indicates that an entity is capable of meeting or exceeding the defined minimum requirements for a given video configuration.
-
D.
supportsH264
Indicates that one entity provides compatibility with, or the ability to encode/decode or process, H.264 video for another entity.
-
E.
supportsDisplayStandard
Indicates that one entity is compatible with and can correctly handle or render the specified display standard.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:51 a.m.