Triple
T20194065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokémon HOME |
E493037
|
entity |
| Predicate | premiumPlanEnables |
P124299
|
FINISHED |
| Object | transfer from Pokémon Bank |
—
|
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: transfer from Pokémon Bank | Statement: [Pokémon HOME, premiumPlanEnables, transfer from Pokémon Bank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiumPlanEnables Context triple: [Pokémon HOME, premiumPlanEnables, transfer from Pokémon Bank]
-
A.
paidTierIncludes
chosen
Indicates that a paid subscription tier encompasses or provides access to a specified feature, service, or benefit.
-
B.
requiresPremiumFor
Indicates that access to or use of something is conditional on having a premium status, subscription, or account.
-
C.
isPremium
Indicates that an entity has premium status, typically granting enhanced or paid-tier features or privileges compared to a standard version.
-
D.
isPremiumTierAvailable
Indicates whether access to a premium-level tier or service option is currently available.
-
E.
hasBasePlan
Indicates that an entity is associated with or derived from a specified foundational or default plan.
- 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.