Triple
T29101471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega TeraDrive |
E736648
|
entity |
| Predicate | secondaryVideoGameCpu |
P31526
|
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: [Sega TeraDrive, secondaryVideoGameCpu, Zilog Z80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryVideoGameCpu Context triple: [Sega TeraDrive, secondaryVideoGameCpu, Zilog Z80]
-
A.
secondaryCpu
chosen
Indicates that one CPU functions as a secondary or backup processor in relation to a primary CPU.
-
B.
videoGame
Indicates that one entity is a video game associated with, created by, or otherwise related to another entity.
-
C.
cpu
Indicates that an entity functions as, contains, or is associated with a central processing unit (CPU) in a computational system.
-
D.
gamePlatformCategory
Indicates the classification or type of platform on which a game is available or intended to be played.
-
E.
videoGamePlatformGeneration
Indicates that a video game platform belongs to, or is classified within, a particular generation of video game hardware or consoles.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 28, 2026, 11:12 a.m.