Triple
T28896126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guard Crush Games |
E732837
|
entity |
| Predicate | workOnFranchise |
P39171
|
FINISHED |
| Object | Streets of Rage 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: Streets of Rage series | Statement: [Guard Crush Games, workOnFranchise, Streets of Rage series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workOnFranchise Context triple: [Guard Crush Games, workOnFranchise, Streets of Rage series]
-
A.
franchiseWorkedOn
chosen
Indicates that an entity has contributed work to, or been professionally involved with, a particular franchise.
-
B.
studioFranchise
Indicates that a studio is associated with, produces, or manages a particular franchise.
-
C.
franchiseContribution
Indicates that an entity provides resources, value, or support to a franchise or franchised operation.
-
D.
franchiseShift
Indicates a change or transfer in control, ownership, or primary association of a franchise from one party or context to another.
-
E.
franchiseFocus
Indicates that an entity (such as a business or organization) is primarily oriented around, dedicated to, or centered on a particular franchise or franchise-related activity.
- 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_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 7:59 a.m.