Triple
T28619114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Direct3D 10 |
E724337
|
entity |
| Predicate | shaderModel |
P164945
|
FINISHED |
| Object | Shader Model 4.0 |
—
|
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: Shader Model 4.0 | Statement: [Direct3D 10, shaderModel, Shader Model 4.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shaderModel Context triple: [Direct3D 10, shaderModel, Shader Model 4.0]
-
A.
shaderUnits
Indicates the relationship between a graphics processor and the number or configuration of its shader processing units used for rendering and computation.
-
B.
supportsShadingLanguage
Indicates that one entity provides compatibility with, or can correctly interpret and execute, a specified shading language used for programmable graphics rendering.
-
C.
supportsMeshShading
Indicates that one entity provides or enables mesh shading functionality for another entity or within a given context.
-
D.
renderingTechnology
Indicates the graphics or visualization method used to generate the visual representation of an object, scene, or interface.
-
E.
materialTechnique
Indicates the materials used and the techniques or methods applied in creating or producing something.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 4:32 a.m.