Triple
T33204441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metal |
E849985
|
entity |
| Predicate | shaderLanguageType |
P84808
|
FINISHED |
| Object | C++-like shading language |
—
|
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: C++-like shading language | Statement: [Metal, shaderLanguageType, C++-like shading language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shaderLanguageType Context triple: [Metal, shaderLanguageType, C++-like shading language]
-
A.
supportsShadingLanguage
chosen
Indicates that one entity provides compatibility with, or can correctly interpret and execute, a specified shading language used for programmable graphics rendering.
-
B.
shaderUnits
Indicates the relationship between a graphics processor and the number or configuration of its shader processing units used for rendering and computation.
-
C.
shaderModel
Indicates the specific graphics shading capability level or version that applies to a rendering process, program, or hardware.
-
D.
compilerType
Indicates the specific kind or category of compiler associated with or used by an entity.
-
E.
compilerLanguage
Indicates that one entity is the programming language in which a given compiler is implemented.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.