Triple
T35194672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mario & Luigi: Superstar Saga + Bowser's Minions |
E1016222
|
entity |
| Predicate | includesPlayableFaction |
P83656
|
FINISHED |
| Object | Bowser's minions |
E391550
|
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: Bowser's minions | Statement: [Mario & Luigi: Superstar Saga + Bowser's Minions, includesPlayableFaction, Bowser's minions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPlayableFaction Context triple: [Mario & Luigi: Superstar Saga + Bowser's Minions, includesPlayableFaction, Bowser's minions]
-
A.
featuresPlayableFaction
chosen
Indicates that a game or scenario includes a faction that players can actively control or play as.
-
B.
isPlayableAllyOf
Indicates that one entity can be used or controlled as an ally in conjunction with another entity, typically within a game or interactive context.
-
C.
gameFaction
Indicates that an entity belongs to, is aligned with, or is a member of a particular faction within a game.
-
D.
hasHeroFaction
Indicates that an entity is associated with or belongs to a particular hero-aligned faction.
-
E.
availableToFaction
Indicates that something can be accessed, used, or obtained by a particular faction.
- F. None of above.
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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38040233a08190affe58b428ec7647 |
completed | June 21, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.