Triple

T17537512
Position Surface form Disambiguated ID Type / Status
Subject Immortalis E427098 entity
Predicate supportsRenderingTechnique P81690 FINISHED
Object ray tracing 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: ray tracing | Statement: [Immortalis, supportsRenderingTechnique, ray tracing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsRenderingTechnique
Context triple: [Immortalis, supportsRenderingTechnique, ray tracing]
  • A. renderingTechnology chosen
    Indicates the graphics or visualization method used to generate the visual representation of an object, scene, or interface.
  • B. supportsRenderingBackend
    Indicates that one entity is capable of using or working with a specified rendering backend to perform rendering operations.
  • C. supportsDisplayTechnology
    Indicates that one entity is compatible with, or capable of operating using, a specified display technology.
  • D. supportsGraphicsSwitching
    Indicates that an entity can dynamically switch between different graphics hardware or rendering modes, typically to balance performance and power usage.
  • E. supportsHardwareAcceleration
    Indicates that one entity enables or provides hardware-based acceleration capabilities for another entity’s operations or processes.
  • 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_69d889de677081909b22d2657b1f0292 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4536dbe908190ba7559f9561f05a2 completed April 19, 2026, 4 a.m.
PD Predicate disambiguation batch_69e3b4f8b9888190aa8a45e09acf4319 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:49 a.m.