Triple
T20983172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starbreeze Studios |
E516818
|
entity |
| Predicate | roleInPaydaySeries |
P142351
|
FINISHED |
| Object | developer |
—
|
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: developer | Statement: [Starbreeze Studios, roleInPaydaySeries, developer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPaydaySeries Context triple: [Starbreeze Studios, roleInPaydaySeries, developer]
-
A.
roleOfCharacter
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
B.
narrativeRoleInSeries
Indicates the specific narrative function or role an entity plays within a particular series or serialized work.
-
C.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
D.
roleInKirbySuperStar
Indicates the specific function or part an entity plays within the context of the game *Kirby Super Star*.
-
E.
roleInHaroldAndKumarSeries
Indicates that an entity portrays a character in the Harold and Kumar film series.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe03244819097630333e70c4e88 |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:48 p.m.