Triple
T37659560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flash Lite |
E937685
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Adobe Flash Player variant |
C49287
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Adobe Flash Player variant Context triple: [Flash Lite, instanceOf, Adobe Flash Player variant]
-
A.
ActionScript Virtual Machine version
An ActionScript Virtual Machine version represents a specific iteration of the runtime environment responsible for executing ActionScript bytecode, defining its supported language features, performance characteristics, and compatibility.
-
B.
Adobe technology
chosen
Adobe technology encompasses a suite of software and cloud-based tools designed for creating, editing, managing, and delivering digital content across media such as graphics, video, documents, and web experiences.
-
C.
adobe pyramid
An adobe pyramid is a monumental, pyramid-shaped structure constructed primarily from sun-dried mud bricks (adobe), typically used for ceremonial, religious, or burial purposes in ancient arid-region cultures.
-
D.
Sprite variant
A Sprite variant represents a specific visual or behavioral version of a base sprite, differing in attributes such as appearance, animation, or effects while retaining the sprite’s core identity.
-
E.
Commodore 64 variant
A Commodore 64 variant is a specific hardware or regional version of the original Commodore 64 home computer, differing in features such as case design, internal components, or market-specific adaptations while remaining broadly software-compatible.
- F. None of above.
Provenance (1 batch)
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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.