Triple
T26032655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raccoon Mario |
E647474
|
entity |
| Predicate | canAttackWith |
P143292
|
FINISHED |
| Object | Tail swipe |
—
|
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: Tail swipe | Statement: [Raccoon Mario, canAttackWith, Tail swipe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canAttackWith Context triple: [Raccoon Mario, canAttackWith, Tail swipe]
-
A.
hasAttack
Indicates that one entity performs, possesses, or is associated with an attack directed toward another entity.
-
B.
attackFeasibility
Indicates the extent to which carrying out an attack is practically possible given current conditions, capabilities, and constraints.
-
C.
hasBaseAttack
Indicates that an entity possesses a fundamental or default attack action or value used as its primary offensive capability.
-
D.
canTarget
chosen
Indicates that one entity is able or permitted to select, aim at, or direct its action or effect toward another entity as a target.
-
E.
hasPrimaryAttack
Indicates that an entity’s main or most frequently used offensive action is another specified entity or attack.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6061b1b5081908dc5e2ac3ac58619 |
completed | May 2, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:06 a.m.