Triple
T29372401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRIS GL |
E744886
|
entity |
| Predicate | graphicsPipelineLevel |
P22768
|
FINISHED |
| Object | immediate-mode API |
—
|
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: immediate-mode API | Statement: [IRIS GL, graphicsPipelineLevel, immediate-mode API]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphicsPipelineLevel Context triple: [IRIS GL, graphicsPipelineLevel, immediate-mode API]
-
A.
pipelineDepth
Indicates the number of sequential processing stages or steps that data or tasks pass through in a pipeline.
-
B.
renderingTechnology
Indicates the graphics or visualization method used to generate the visual representation of an object, scene, or interface.
-
C.
graphicsAPI
chosen
Indicates a relationship where one entity uses, supports, or is implemented with a particular graphics application programming interface (graphicsAPI).
-
D.
shaderModel
Indicates the specific graphics shading capability level or version that applies to a rendering process, program, or hardware.
-
E.
supportsShadingLanguage
Indicates that one entity provides compatibility with, or can correctly interpret and execute, a specified shading language used for programmable graphics rendering.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669ab36008190bc2e3c5dbdd2050d |
completed | May 2, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 2:28 p.m.