Triple
T30422197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sam440ep motherboard |
E773928
|
entity |
| Predicate | supportsEndianMode |
P11220
|
FINISHED |
| Object | big-endian |
—
|
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: big-endian | Statement: [Sam440ep motherboard, supportsEndianMode, big-endian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsEndianMode Context triple: [Sam440ep motherboard, supportsEndianMode, big-endian]
-
A.
endianess
Indicates the byte order relationship specifying how multi-byte data is arranged in memory or during transmission (e.g., little-endian vs big-endian).
-
B.
endiannessDependent
Indicates that the relationship or behavior varies depending on the byte-order (endianness) used to represent multi-byte data.
-
C.
isEndiannessAgnostic
Indicates that the behavior or data format is independent of byte order, producing correct results regardless of the system’s endianness.
-
D.
endianness
chosen
Indicates the ordering of bytes used to represent multi-byte data values in memory or storage.
-
E.
supportsByteAddressing
Indicates that one entity provides the capability for direct access to individual bytes within its addressable memory or data space for another entity.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:06 p.m.