Triple
T20165090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mario & Luigi: Bowser’s Inside Story |
E491806
|
entity |
| Predicate | combatView |
P138911
|
FINISHED |
| Object | side-view battle screen |
—
|
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: side-view battle screen | Statement: [Mario & Luigi: Bowser’s Inside Story, combatView, side-view battle screen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatView Context triple: [Mario & Luigi: Bowser’s Inside Story, combatView, side-view battle screen]
-
A.
combatBy
Indicates a relationship where one entity engages in combat or fighting through the agency, actions, or involvement of another entity.
-
B.
combat
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
-
C.
combatIndicator
Indicates that an entity is involved in, associated with, or signaling the occurrence of combat or hostile activity.
-
D.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
E.
battleTarget
Indicates that one entity is the chosen opponent or objective that another entity is engaging or intends to engage in battle.
- 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.