Triple
T29858313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATI Xenos |
E758248
|
entity |
| Predicate | shaderModelSupport |
P164945
|
FINISHED |
| Object | Shader Model 3.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 3.0+ | Statement: [ATI Xenos, shaderModelSupport, Shader Model 3.0+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shaderModelSupport Context triple: [ATI Xenos, shaderModelSupport, Shader Model 3.0+]
-
A.
shaderModel
chosen
Indicates the specific graphics shading capability level or version that applies to a rendering process, program, or hardware.
-
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.
supportsMultisampling
Indicates that an entity provides or enables multisampling functionality, typically for improved rendering quality.
-
E.
renderingTechnology
Indicates the graphics or visualization method used to generate the visual representation of an object, scene, or interface.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6768345fc8190bdc72aa7af054375 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:47 p.m.