Triple
T20165088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mario & Luigi: Bowser’s Inside Story |
E491806
|
entity |
| Predicate | remakeIncludes |
P138910
|
FINISHED |
| Object | Bowser Jr.’s Journey side story |
—
|
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: Bowser Jr.’s Journey side story | Statement: [Mario & Luigi: Bowser’s Inside Story, remakeIncludes, Bowser Jr.’s Journey side story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remakeIncludes Context triple: [Mario & Luigi: Bowser’s Inside Story, remakeIncludes, Bowser Jr.’s Journey side story]
-
A.
renamedToInclude
Indicates that an entity has been renamed so that its new name explicitly includes another specified element (such as a term, identifier, or component).
-
B.
hasRemake
Indicates that one work is a new version or recreation of an earlier existing work.
-
C.
remnantsInclude
Indicates that the remaining parts or leftovers of one entity contain or consist of another entity.
-
D.
collectiveIncludes
Indicates that a collective entity contains or comprises the specified member or subset as part of its whole.
-
E.
remadeFor
Indicates that one work has been recreated or adapted specifically for another context, audience, or medium.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6684376408190a68890ab48fa5424 |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:35 p.m.