Triple
T8820766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SceneKit |
E209895
|
entity |
| Predicate | supportsOffscreenRendering |
P84810
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SceneKit, supportsOffscreenRendering, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOffscreenRendering Context triple: [SceneKit, supportsOffscreenRendering, true]
-
A.
supportsCompositingBackend
Indicates that one entity provides compatibility with or can operate using a specified compositing backend.
-
B.
supportsHardwareAcceleration
Indicates that one entity enables or provides hardware-based acceleration capabilities for another entity’s operations or processes.
-
C.
supportsOverscan
Indicates that a display device or system is capable of handling overscan, meaning it can properly show content that extends beyond the nominal visible screen area.
-
D.
supportsExternalDisplay
Indicates that an entity is capable of connecting to and functioning with an external display device.
-
E.
supports3DAcceleration
Indicates that one entity provides or enables hardware- or software-based 3D graphics acceleration for another entity.
- F. None of above. chosen
Provenance (4 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc601126248190b6f10c22f1aeac9a |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:46 p.m.