Triple
T29392041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPI |
E745388
|
entity |
| Predicate | supportsBitOrder |
—
|
GENERATED |
| Object | LSB first (implementation dependent) |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBitOrder Context triple: [SPI, supportsBitOrder, LSB first (implementation dependent)]
-
A.
bitOrder
chosen
Indicates the ordering or sequence of bits within a binary representation, such as which bit positions are considered first or most significant.
-
B.
bitSynchronizationSupport
Indicates whether a system, device, or protocol provides mechanisms to align and maintain timing at the bit level between communicating entities.
-
C.
isBitField
Indicates that a value, variable, or field is treated as a bit field, meaning its individual bits represent distinct flags or sub-values rather than a single scalar quantity.
-
D.
supportsBitDepthUpTo
Indicates the maximum bit depth value that an entity can handle, process, or is compatible with.
-
E.
hasBit
Indicates that one entity possesses, contains, or includes a specific bit or binary position/value of another entity.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:43 p.m.