Triple
T28612954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega arcade systems |
E724210
|
entity |
| Predicate | hardwareGenerationSpan |
P98536
|
FINISHED |
| Object | 1980s to 2010s |
—
|
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: 1980s to 2010s | Statement: [Sega arcade systems, hardwareGenerationSpan, 1980s to 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardwareGenerationSpan Context triple: [Sega arcade systems, hardwareGenerationSpan, 1980s to 2010s]
-
A.
chipsetGeneration
Indicates the generation or version lineage to which a particular chipset belongs.
-
B.
targetDeviceGeneration
Indicates the specific hardware or model generation of the device that is the focus or recipient of an action or relationship.
-
C.
targetPlatformGeneration
Indicates the generation or version of the platform that an action, resource, or entity is specifically intended to run on or be compatible with.
-
D.
microprocessorGeneration
Indicates the specific technological generation or iteration to which a given microprocessor belongs.
-
E.
platformGenerationScope
chosen
Indicates the range or context within which a platform is created, applied, or considered valid.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:30 a.m.