Triple
T20192972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokémon Trading Card Game |
E493016
|
entity |
| Predicate | usesRandomDistribution |
P83418
|
FINISHED |
| Object | booster packs |
—
|
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: booster packs | Statement: [Pokémon Trading Card Game, usesRandomDistribution, booster packs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRandomDistribution Context triple: [Pokémon Trading Card Game, usesRandomDistribution, booster packs]
-
A.
isRandomized
chosen
Indicates that the selection, ordering, or assignment associated with something is determined by a random process rather than a fixed or predetermined rule.
-
B.
canBeRandomized
Indicates that the entity is capable of having its state, order, or selection determined by a random process.
-
C.
defaultRNGType
Indicates the standard or primary random number generator type that should be used when no specific RNG type is explicitly chosen.
-
D.
hasDistributionFunction
Indicates that an entity is associated with a specific distribution function that characterizes how its values or occurrences are probabilistically or statistically distributed.
-
E.
uniformDistinction
Indicates that a clear and consistent difference is maintained between two or more entities within a given context.
- 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_69e66ad7270081908ed8513a8363e9b1 |
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.