Triple
T27885329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Core m3-7Y30 |
E705207
|
entity |
| Predicate | supportsIntelClearVideoHD |
P201866
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Intel Core m3-7Y30, supportsIntelClearVideoHD, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIntelClearVideoHD Context triple: [Intel Core m3-7Y30, supportsIntelClearVideoHD, true]
-
A.
supportsDisplayResolution
Indicates that one entity is capable of operating with, rendering, or otherwise accommodating the specified display resolution of another entity.
-
B.
hasHDMIPort
Indicates that one entity (typically a device) is equipped with an HDMI port that can be used to connect to another entity.
-
C.
supportsIntelQuickSyncVideo
Indicates that one entity provides compatibility with or functional support for Intel Quick Sync Video hardware-accelerated video processing.
-
D.
supportsDisplayStandard
Indicates that one entity is compatible with and can correctly handle or render the specified display standard.
-
E.
supportsDisplayTechnology
Indicates that one entity is compatible with, or capable of operating using, a specified display technology.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
| PDg | Predicate description generation | batch_6a002dd3294881909e860157fc459a85 |
completed | May 10, 2026, 7:03 a.m. |
Created at: April 27, 2026, 6:32 p.m.