Triple
T7980229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel UHD Graphics 615 |
E185551
|
entity |
| Predicate | shaderUnits |
P80140
|
FINISHED |
| Object | 24 execution units |
—
|
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: 24 execution units | Statement: [Intel UHD Graphics 615, shaderUnits, 24 execution units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shaderUnits Context triple: [Intel UHD Graphics 615, shaderUnits, 24 execution units]
-
A.
componentProgram
Indicates that one entity is a component or module that forms part of a larger program or software system represented by the other entity.
-
B.
supportsMeshShading
Indicates that one entity provides or enables mesh shading functionality for another entity or within a given context.
-
C.
usesUniform
Indicates that one entity regularly wears or employs a standardized set of clothing or equipment designated as a uniform.
-
D.
integratesGPU
Indicates that one entity incorporates or embeds a GPU as a functional component within its design or system.
-
E.
coreUnitType
Indicates that one entity is classified as the primary or fundamental type/category to which another entity (a core unit) belongs.
- 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_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. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:14 p.m.