Triple
T38643900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mythic+ dungeons |
E938668
|
entity |
| Predicate | timeLimitAffects |
P176220
|
FINISHED |
| Object | keystone upgrade amount |
—
|
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: keystone upgrade amount | Statement: [Mythic+ dungeons, timeLimitAffects, keystone upgrade amount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeLimitAffects Context triple: [Mythic+ dungeons, timeLimitAffects, keystone upgrade amount]
-
A.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
B.
timeThreshold
chosen
Indicates a temporal limit or cutoff point after which a related condition, event, or state changes or no longer applies.
-
C.
timeAfterAble
Indicates that one event, state, or action occurs after another point in time at which it becomes possible or permissible.
-
D.
timeSensitivity
Indicates how strongly the relationship or action depends on, changes with, or is constrained by time.
-
E.
agingTimeMaximum
Indicates the maximum duration for which something is allowed or expected to age before it is considered expired, mature, or no longer valid.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.