Triple
T20194508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunder Shock |
E493046
|
entity |
| Predicate | maxMovePower |
P118392
|
FINISHED |
| Object | Max Lightning 90 |
—
|
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: Max Lightning 90 | Statement: [Thunder Shock, maxMovePower, Max Lightning 90]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxMovePower Context triple: [Thunder Shock, maxMovePower, Max Lightning 90]
-
A.
powerLevel
Indicates the degree or intensity of power or strength possessed by an entity in a given context.
-
B.
maximumEnergy
chosen
Indicates the greatest amount of energy that an entity can possess, store, or output under specified conditions.
-
C.
maximumTorque
Indicates the greatest amount of torque that can be produced, transmitted, or withstood in the specified context.
-
D.
maximumPowerAtPSE
Indicates the highest level of power that can be delivered or drawn at the Power Sourcing Equipment (PSE) in the relationship.
-
E.
strengthenedPowerIn
Indicates that one entity has increased, reinforced, or consolidated its power, influence, or control within a particular context, domain, or location represented by the other entity.
- 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_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.