Triple
T20194447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volt Tackle |
E493045
|
entity |
| Predicate | recoilPercentage |
P92182
|
FINISHED |
| Object | 1/3 of damage dealt |
—
|
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: 1/3 of damage dealt | Statement: [Volt Tackle, recoilPercentage, 1/3 of damage dealt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recoilPercentage Context triple: [Volt Tackle, recoilPercentage, 1/3 of damage dealt]
-
A.
recoilLevel
Indicates the degree or intensity of backward force or kick produced when an action (such as firing a weapon or operating a device) occurs.
-
B.
percentageForChange
Indicates the proportion or rate, expressed as a percentage, by which something increases, decreases, or otherwise changes relative to a reference value.
-
C.
percentage
chosen
Indicates the proportion or share of one quantity relative to another, typically expressed as a value out of 100.
-
D.
OnBasePercentage
Indicates the frequency with which a batter successfully reaches base (by hit, walk, or hit-by-pitch) per plate appearance.
-
E.
goalPercentage
Indicates the proportion of a goal that has been achieved relative to its total target.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad7ed548190a893110fa2ffb144 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.