Triple
T30358668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Mark III |
E772212
|
entity |
| Predicate | hardwarePredecessor |
P9736
|
FINISHED |
| Object | SG-1000 II |
—
|
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: SG-1000 II | Statement: [Sega Mark III, hardwarePredecessor, SG-1000 II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardwarePredecessor Context triple: [Sega Mark III, hardwarePredecessor, SG-1000 II]
-
A.
predecessorSystem
chosen
Indicates that one system existed or was in use before and was replaced or superseded by another system.
-
B.
predecessorSystemType
Indicates that one system type functioned as the predecessor or earlier version to another system type.
-
C.
predecessorCpuArchitecture
Indicates that one CPU architecture directly precedes another in an evolutionary or historical development sequence.
-
D.
predecessorPlatformCode
Indicates that one platform’s code identifies a platform that directly preceded another in a sequence or version lineage.
-
E.
previouslySupportedHardware
Indicates that the subject hardware was supported in the past but is no longer currently supported.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682417ec08190982dd9acf7219742 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 7:57 p.m.