Triple
T26176666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilog |
E654560
|
entity |
| Predicate | Z80BusWidth |
P4121
|
FINISHED |
| Object | 8-bit data bus |
—
|
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: 8-bit data bus | Statement: [Zilog, Z80BusWidth, 8-bit data bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Z80BusWidth Context triple: [Zilog, Z80BusWidth, 8-bit data bus]
-
A.
busWidthComparedToISA
Indicates how the width of a bus compares to the width defined by a given instruction set architecture (ISA), such as being wider, narrower, or equal.
-
B.
bitWidth
chosen
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
C.
supportsByteAddressing
Indicates that one entity provides the capability for direct access to individual bytes within its addressable memory or data space for another entity.
-
D.
nuBusSlotsCount
Indicates the number of bus slots associated with or available on a given entity.
-
E.
L2CacheBusWidth
Indicates the width of the data bus used to connect to the Level 2 (L2) cache, typically measured in bits.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c6c9b808190812dcb252b9844f2 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:38 p.m.