Triple
T29100324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extra Half-Brite |
E736622
|
entity |
| Predicate | usesBitplanes |
P173254
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Extra Half-Brite, usesBitplanes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBitplanes Context triple: [Extra Half-Brite, usesBitplanes, yes]
-
A.
extraBitplanesUsedFor
Indicates that additional bitplanes are utilized to provide extra data or capabilities for a specified target (such as an image, layer, or graphical element).
-
B.
bitplaneCount
Indicates the number of distinct bitplanes (separate layers of bit-level data) used to represent or encode a value or image.
-
C.
supportsAlphaBitDepth
Indicates that one entity is capable of handling or providing image or video data with an alpha (transparency) channel at a specified bit depth.
-
D.
supportsInterlacing
Indicates that one entity is capable of handling or enabling interlaced data or processing for another entity.
-
E.
colorDepth
Indicates the bit-depth used to represent the color information of an image or display, defining how many distinct colors can be shown.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 28, 2026, 11:11 a.m.