Triple
T28895941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Hunter |
E732832
|
entity |
| Predicate | returnAsPlayable |
P88329
|
FINISHED |
| Object | Streets of Rage 4 |
—
|
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 4 | Statement: [Adam Hunter, returnAsPlayable, Streets of Rage 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnAsPlayable Context triple: [Adam Hunter, returnAsPlayable, Streets of Rage 4]
-
A.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
B.
playableInGame
chosen
Indicates that something can be used or controlled as an active element within a particular game.
-
C.
playableMode
Indicates that a particular mode, configuration, or state can be actively used or played within a system or application.
-
D.
playableSide
Indicates that a particular side, faction, or team in a game can be actively controlled or chosen by the player.
-
E.
returnedAs
Indicates that one entity is given back or sent back to another entity or to its original source, typically as the outcome of a prior transfer, request, or operation.
- 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_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 7:59 a.m.