Triple
T7980187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Core m3-8100Y |
E185550
|
entity |
| Predicate | maxResolutionHDMI |
P74451
|
FINISHED |
| Object | 4096x2304@24Hz |
—
|
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: 4096x2304@24Hz | Statement: [Intel Core m3-8100Y, maxResolutionHDMI, 4096x2304@24Hz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxResolutionHDMI Context triple: [Intel Core m3-8100Y, maxResolutionHDMI, 4096x2304@24Hz]
-
A.
maximumResolution
Indicates the highest level of detail or fineness at which something (such as an image, display, or measurement) can be represented or processed.
-
B.
supportsDisplayResolution
chosen
Indicates that one entity is capable of operating with, rendering, or otherwise accommodating the specified display resolution of another entity.
-
C.
hdmiVersion
Indicates the specific HDMI standard or version associated with a device, port, or connection.
-
D.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
-
E.
maximumBitrate
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c274ce48190854d389d43ce14b8 |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:14 p.m.