Triple
T26333594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilog Z8000 |
E662458
|
entity |
| Predicate | supports32BitRegistersViaPairing |
P196453
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zilog Z8000, supports32BitRegistersViaPairing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supports32BitRegistersViaPairing Context triple: [Zilog Z8000, supports32BitRegistersViaPairing, true]
-
A.
supports32bitOperatingSystems
Indicates that the subject is compatible with and can properly run 32-bit operating systems.
-
B.
canPairRegistersFor
Indicates that two registers are compatible and allowed to be paired together for a combined or coordinated operation.
-
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.
supports64BitApps
Indicates that the subject is capable of running or is compatible with 64-bit applications.
-
E.
supportsBigLittleHybrid
Indicates that an entity is compatible with or enables operation using a big.LITTLE-style heterogeneous core or component configuration.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
| PDg | Predicate description generation | batch_69fe38bc3e9c8190838430b22b82503f |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 26, 2026, 10:35 p.m.