Triple
T26333598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilog Z8000 |
E662458
|
entity |
| Predicate | hasOnChipMMUVariant |
P87753
|
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, hasOnChipMMUVariant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnChipMMUVariant Context triple: [Zilog Z8000, hasOnChipMMUVariant, true]
-
A.
hasIntegratedMMU
chosen
Indicates that a system or processor includes a built-in Memory Management Unit (MMU) as part of its architecture.
-
B.
hasOnChip
Indicates that one component or system includes another component integrated directly onto the same chip or integrated circuit.
-
C.
hasOnChipCache
Indicates that one hardware component includes an integrated cache memory directly on the same chip.
-
D.
usedWithChipsetsFrom
Indicates that something is designed or suitable to be used together with specific chipsets from a given manufacturer or family.
-
E.
hasLowPowerVariant
Indicates that an entity has a related version or configuration designed to operate with reduced power consumption compared to the standard one.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 10:35 p.m.