Triple
T5072822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bowser Jr. Shadow Showdown |
E114320
|
entity |
| Predicate | usesGameplayMechanic |
P8166
|
FINISHED |
| Object | shadow gameplay |
—
|
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: shadow gameplay | Statement: [Bowser Jr. Shadow Showdown, usesGameplayMechanic, shadow gameplay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGameplayMechanic Context triple: [Bowser Jr. Shadow Showdown, usesGameplayMechanic, shadow gameplay]
-
A.
gameplayMechanic
Indicates a relationship where one entity functions as a rule, system, or interactive feature that defines how another entity can be played or operated within a game.
-
B.
performedInGame
Indicates that an action or event was carried out during a particular game or match.
-
C.
hasMechanism
chosen
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
D.
mentionsMechanism
Indicates that one entity explicitly refers to or describes the mechanism, process, or causal pathway by which another entity operates or produces an effect.
-
E.
definesMechanism
Indicates that one entity specifies or explains the underlying process or mechanism by which another entity operates or occurs.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74cfa4348190bc50590117a6bcf9 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.