Triple
T20263039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raichu |
E498890
|
entity |
| Predicate | signatureMoveUser |
P108696
|
FINISHED |
| Object | Volt Tackle (via breeding as Pikachu line) |
—
|
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: Volt Tackle (via breeding as Pikachu line) | Statement: [Raichu, signatureMoveUser, Volt Tackle (via breeding as Pikachu line)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureMoveUser Context triple: [Raichu, signatureMoveUser, Volt Tackle (via breeding as Pikachu line)]
-
A.
usesSignatureMove
chosen
Indicates that an entity performs or employs a distinctive, characteristic move or technique associated specifically with it.
-
B.
membershipTransfer
Indicates the transfer of membership status, rights, or affiliation from one entity to another.
-
C.
movedBy
Indicates that an entity changes position or location as a result of another entity’s action or influence.
-
D.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
E.
signFeature
Indicates that an entity bears or displays a particular sign, symbol, or distinguishing feature.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674ccff008190920b418f51dc4311 |
completed | April 20, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.