Triple
T3778116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Sports |
E83355
|
entity |
| Predicate | notablePlatformEra |
P50875
|
FINISHED |
| Object | sixth 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: sixth generation of video game consoles | Statement: [Sega Sports, notablePlatformEra, sixth generation of video game consoles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlatformEra Context triple: [Sega Sports, notablePlatformEra, sixth generation of video game consoles]
-
A.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
B.
notableEraStart
Indicates the point in time when a notable or historically significant era associated with an entity begins.
-
C.
notableEraNickname
Indicates the informal or popular nickname by which a particular historical era or period is commonly known.
-
D.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
E.
notableEraTeam2
Indicates that the second team is notably associated with, or prominent during, a particular historical era or period.
- F. None of above. chosen
Provenance (4 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc5d3dbc8190b6ab118a56acd5a3 |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc0fe3e3c8190bd886c7745c172a0 |
completed | March 8, 2026, 6:33 p.m. |
Created at: March 8, 2026, 3:36 p.m.