Triple
T29035610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Genesis Model 1 |
E737849
|
entity |
| Predicate | secondaryCpuRole |
P2114
|
FINISHED |
| Object | sound controller |
—
|
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: sound controller | Statement: [Sega Genesis Model 1, secondaryCpuRole, sound controller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryCpuRole Context triple: [Sega Genesis Model 1, secondaryCpuRole, sound controller]
-
A.
secondaryCpu
Indicates that one CPU functions as a secondary or backup processor in relation to a primary CPU.
-
B.
secondaryProcess
Indicates that an action or process occurs as a secondary, supporting, or subordinate operation relative to a primary process.
-
C.
secondaryFunction
chosen
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
D.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
E.
primaryCpu
Indicates that one CPU is designated as the main or primary processing unit in relation to another component or system.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 28, 2026, 9:58 a.m.