Triple
T15534650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosalina (Super Smash Bros. series) |
E370310
|
entity |
| Predicate | specialMove |
P118339
|
FINISHED |
| Object | Luma Shot |
—
|
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: Luma Shot | Statement: [Rosalina (Super Smash Bros. series), specialMove, Luma Shot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialMove Context triple: [Rosalina (Super Smash Bros. series), specialMove, Luma Shot]
-
A.
SmashBrosSpecialMove
chosen
Indicates that one character performs a unique special move or attack on another character within the context of a Super Smash Bros. match.
-
B.
specialAppearance
Indicates that an entity makes a notable or exceptional appearance distinct from its usual or regular presence.
-
C.
spellSpecialty
Indicates that an entity’s area of expertise or focus is a particular type or category of spell.
-
D.
spinAttackEffect
Indicates an effect that occurs when an entity performs or is subjected to a spinning attack action.
-
E.
ultimateAbility
Indicates that an entity possesses or uses its most powerful, defining special ability or move.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.