Triple
T26176646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilog |
E654560
|
entity |
| Predicate | notableCPU |
P8608
|
FINISHED |
| Object | Zilog Z80 |
—
|
NE NERFINISHED |
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: Zilog Z80 | Statement: [Zilog, notableCPU, Zilog Z80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCPU Context triple: [Zilog, notableCPU, Zilog Z80]
-
A.
cpu
chosen
Indicates that an entity functions as, contains, or is associated with a central processing unit (CPU) in a computational system.
-
B.
typicalCPU
Indicates that an entity uses or is associated with a standard or commonly used CPU for its type or category.
-
C.
notableSystem
Indicates that a system is recognized as significant, prominent, or noteworthy in a particular context or domain.
-
D.
notableConsoleFamily
Indicates that a video game console belongs to a family or line of consoles that is considered particularly significant or prominent.
-
E.
hasCPUDetails
Indicates that an entity is associated with specific information or specifications about its CPU.
- 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_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: April 26, 2026, 8:38 p.m.