Triple
T19974722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Squirtle |
E493660
|
entity |
| Predicate | hasBaseSpecialAttack |
P138111
|
FINISHED |
| Object | 50 |
—
|
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: 50 | Statement: [Squirtle, hasBaseSpecialAttack, 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseSpecialAttack Context triple: [Squirtle, hasBaseSpecialAttack, 50]
-
A.
hasPrimaryAttack
Indicates that an entity’s main or most frequently used offensive action is another specified entity or attack.
-
B.
hasBaseDefense
Indicates that an entity possesses a specified level or value of defensive capability in its default or starting state.
-
C.
hasAttack
Indicates that one entity performs, possesses, or is associated with an attack directed toward another entity.
-
D.
hasHeroPower
Indicates that one entity possesses or is endowed with a special ability or power characteristic of a hero in relation to another entity.
-
E.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
- F. None of above. chosen
Provenance (4 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65bcca5088190b523584d11799400 |
completed | April 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:24 p.m.