Triple
T8472782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega |
E200316
|
entity |
| Predicate | notableConsoleGeneration |
P12591
|
FINISHED |
| Object | fourth generation of video game consoles |
—
|
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: fourth generation of video game consoles | Statement: [Sega, notableConsoleGeneration, fourth generation of video game consoles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableConsoleGeneration Context triple: [Sega, notableConsoleGeneration, fourth generation of video game consoles]
-
A.
notableConsoleFamily
Indicates that a video game console belongs to a family or line of consoles that is considered particularly significant or prominent.
-
B.
notableGeneration
chosen
Indicates that an entity is particularly distinguished or recognized among a specific generation or cohort.
-
C.
notablePlatformEra
Indicates that an entity is notably associated with a particular platform during a specific era or period of prominence.
-
D.
notableDeviceLine
Indicates that a device is a prominent or well-known product line associated with an entity.
-
E.
notableEngineFamily
Indicates that one entity is a well-known or significant engine family associated with the other entity.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f4fbf481909e4fd7c078b27477 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.