Triple
T36549299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LithTech |
E901214
|
entity |
| Predicate | renderingAPI |
P22768
|
FINISHED |
| Object | Direct3D |
—
|
NE NERFINISHED |
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: Direct3D | Statement: [LithTech, renderingAPI, Direct3D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renderingAPI Context triple: [LithTech, renderingAPI, Direct3D]
-
A.
graphicsAPI
chosen
Indicates a relationship where one entity uses, supports, or is implemented with a particular graphics application programming interface (graphicsAPI).
-
B.
renderingTechnology
Indicates the graphics or visualization method used to generate the visual representation of an object, scene, or interface.
-
C.
renderingMode
Indicates the specific way in which content or graphics are processed and displayed (e.g., style, technique, or pipeline used for rendering).
-
D.
renderingArchitecture
Indicates the specific rendering system or framework used to generate visual output for a given entity or environment.
-
E.
supportsRenderingBackend
Indicates that one entity is capable of using or working with a specified rendering backend to perform rendering operations.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.