Triple
T29456579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HAM-8 display mode |
E747117
|
entity |
| Predicate | bitUsage |
P4121
|
FINISHED |
| Object | 2 control bits and 6 data bits |
—
|
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: 2 control bits and 6 data bits | Statement: [HAM-8 display mode, bitUsage, 2 control bits and 6 data bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bitUsage Context triple: [HAM-8 display mode, bitUsage, 2 control bits and 6 data bits]
-
A.
bitWidth
chosen
Indicates the number of bits used to represent or encode a given value, type, or data 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.
bitOrder
Indicates the ordering or sequence of bits within a binary representation, such as which bit positions are considered first or most significant.
-
D.
bitSlice
Indicates taking a contiguous subset of bits from a larger bit sequence, defined by specified start and end positions.
-
E.
spaceUsage
Indicates how much physical or storage space is occupied or utilized by an entity relative to the total available space.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66b6cf8fc81909cd68959b362dde0 |
completed | May 2, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:46 p.m.