Triple
T29372262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capcom CPS-1 |
E744883
|
entity |
| Predicate | notableGameSeries |
P204240
|
FINISHED |
| Object | Street Fighter II series |
E495984
|
NE 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: Street Fighter II series | Statement: [Capcom CPS-1, notableGameSeries, Street Fighter II series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGameSeries Context triple: [Capcom CPS-1, notableGameSeries, Street Fighter II series]
-
A.
publishedGameSeries
Indicates that a publisher has released or made available a particular game series to the public.
-
B.
seriesGame
Indicates that a game is part of, or belongs to, a particular series or franchise.
-
C.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
-
D.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
E.
notableConsoleGame
Indicates that a game is recognized as a significant or prominent title released for a particular video game console.
- F. None of above. chosen
Provenance (5 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a03544239d4819087b6c232d6804977 |
completed | May 12, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25f0fbcfcc8190b76da4050a9ac317 |
completed | June 7, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_6a0353d685688190b01df77fc2f62bf2 |
completed | May 12, 2026, 4:22 p.m. |
| PDg | Predicate description generation | batch_6a03544190608190aa659147c9956a3c |
completed | May 12, 2026, 4:24 p.m. |
Created at: April 28, 2026, 2:28 p.m.