Triple
T8985478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Genesis Model 2 |
E214651
|
entity |
| Predicate | secondaryProcessorUse |
P31526
|
FINISHED |
| Object | sound control |
—
|
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 control | Statement: [Sega Genesis Model 2, secondaryProcessorUse, sound control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryProcessorUse Context triple: [Sega Genesis Model 2, secondaryProcessorUse, sound control]
-
A.
secondaryProcess
Indicates that an action or process occurs as a secondary, supporting, or subordinate operation relative to a primary process.
-
B.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
C.
secondaryCpu
chosen
Indicates that one CPU functions as a secondary or backup processor in relation to a primary CPU.
-
D.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
E.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67eddbf08190afca16e0be435241 |
completed | April 1, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:03 p.m.