Triple
T29341309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GrimE |
E744043
|
entity |
| Predicate | graphicsTechnology |
P81690
|
FINISHED |
| Object | 3D graphics |
—
|
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: 3D graphics | Statement: [GrimE, graphicsTechnology, 3D graphics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphicsTechnology Context triple: [GrimE, graphicsTechnology, 3D graphics]
-
A.
renderingTechnology
chosen
Indicates the graphics or visualization method used to generate the visual representation of an object, scene, or interface.
-
B.
graphicsAPI
Indicates a relationship where one entity uses, supports, or is implemented with a particular graphics application programming interface (graphicsAPI).
-
C.
supportsGraphicsSwitching
Indicates that an entity can dynamically switch between different graphics hardware or rendering modes, typically to balance performance and power usage.
-
D.
graphicsArchitecture
Indicates the underlying design or structural framework that defines how a system’s graphics or visual rendering components are organized and operate.
-
E.
graphicsCapabilities
Indicates the level or type of graphical processing features or performance that an entity supports or provides.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66926e7a48190a1b580fd9fe67c31 |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:34 p.m.