Triple
T9183405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Genesis Model 3 |
E220389
|
entity |
| Predicate | hasSecondaryCPU |
P31526
|
FINISHED |
| Object | Zilog Z80-compatible audio and I/O CPU |
—
|
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: Zilog Z80-compatible audio and I/O CPU | Statement: [Sega Genesis Model 3, hasSecondaryCPU, Zilog Z80-compatible audio and I/O CPU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryCPU Context triple: [Sega Genesis Model 3, hasSecondaryCPU, Zilog Z80-compatible audio and I/O CPU]
-
A.
secondaryCpu
chosen
Indicates that one CPU functions as a secondary or backup processor in relation to a primary CPU.
-
B.
hasSecondaryCore
Indicates that an entity possesses an additional, subordinate core component alongside its primary core.
-
C.
hasCPUCore
Indicates that an entity (typically a computing device or processor) possesses or includes a specific CPU core as one of its components.
-
D.
supportsDualProcessors
Indicates that an entity is capable of operating with or accommodating two processors simultaneously.
-
E.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc31734908190b8ebe3b57849ca5f |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.