Triple
T30756903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genjuro Kibagami |
E783111
|
entity |
| Predicate | specialMoveType |
P180031
|
FINISHED |
| Object | card-based slashes |
—
|
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: card-based slashes | Statement: [Genjuro Kibagami, specialMoveType, card-based slashes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialMoveType Context triple: [Genjuro Kibagami, specialMoveType, card-based slashes]
-
A.
SmashBrosSpecialMove
Indicates that one character performs a unique special move or attack on another character within the context of a Super Smash Bros. match.
-
B.
superMove
chosen
Indicates a special or exceptionally powerful movement or action performed beyond normal capabilities.
-
C.
hasBaseSpecialAttack
Indicates that an entity possesses a specified base value for its special attack attribute.
-
D.
specialWeapon
Indicates that an entity is a weapon with unique, enhanced, or otherwise exceptional properties compared to standard weapons.
-
E.
specialAppearance
Indicates that an entity makes a notable or exceptional appearance distinct from its usual or regular presence.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 29, 2026, 8:39 p.m.