Triple
T28896729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Genesis Classics collections |
E732852
|
entity |
| Predicate | includesGameFromSeries |
P61398
|
FINISHED |
| Object | Sonic the Hedgehog series |
—
|
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: Sonic the Hedgehog series | Statement: [Sega Genesis Classics collections, includesGameFromSeries, Sonic the Hedgehog series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesGameFromSeries Context triple: [Sega Genesis Classics collections, includesGameFromSeries, Sonic the Hedgehog series]
-
A.
seriesGame
Indicates that a game is part of, or belongs to, a particular series or franchise.
-
B.
gamesInSeries
chosen
Indicates that the related entities are individual games that belong to the same overarching game series or franchise.
-
C.
publishedGameSeries
Indicates that a publisher has released or made available a particular game series to the public.
-
D.
includesGameType
Indicates that one entity contains or supports a particular type or category of game.
-
E.
seriesIncludes
Indicates that a particular series contains or encompasses the referenced item as one of its constituent parts.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: April 28, 2026, 7:59 a.m.