Triple
T34008902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gambler’s Roll |
E872046
|
entity |
| Predicate | hasCooldown |
P63769
|
FINISHED |
| Object | shared Phantom Roll recast timer |
—
|
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: shared Phantom Roll recast timer | Statement: [Gambler’s Roll, hasCooldown, shared Phantom Roll recast timer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCooldown Context triple: [Gambler’s Roll, hasCooldown, shared Phantom Roll recast timer]
-
A.
cooldown
chosen
Indicates that an entity must wait a specified period of time before performing the same action or a related action again.
-
B.
cooldownStarts
Indicates that a cooldown period for an action or entity begins at a specific point in time.
-
C.
hasCadence
Indicates that something possesses or exhibits a particular rhythmic pattern, tempo, or flow.
-
D.
hasFreezingPeriod
Indicates that an entity is subject to a defined time interval during which freezing (e.g., of assets, operations, or conditions) is in effect.
-
E.
hasColdPhase
Indicates that an entity undergoes or includes a period or stage characterized by low temperature or cold conditions.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:51 a.m.