Triple
T9477242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shell Toss |
E228545
|
entity |
| Predicate | isUnaffectedBy |
P67874
|
FINISHED |
| Object | Mario’s badges that only affect Mario’s own attacks |
—
|
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: Mario’s badges that only affect Mario’s own attacks | Statement: [Shell Toss, isUnaffectedBy, Mario’s badges that only affect Mario’s own attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnaffectedBy Context triple: [Shell Toss, isUnaffectedBy, Mario’s badges that only affect Mario’s own attacks]
-
A.
areAffectedBy
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
B.
isResistant
chosen
Indicates that an entity can withstand, oppose, or is not significantly affected by a specified force, influence, or agent.
-
C.
affectsVariant
Indicates that one entity has an influence or impact on a specific variant or version of another entity.
-
D.
effectOnOthers
Indicates the impact or influence that one entity’s actions, presence, or state has on other entities.
-
E.
isUndefeated
Indicates that an entity has not been defeated in any relevant contest, match, or competition.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd801386948190890133f622ff360b |
completed | April 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.