Triple
T38586307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cataclysm |
E932352
|
entity |
| Predicate | levelCapIncrease |
P187846
|
FINISHED |
| Object | 80 to 85 |
—
|
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: 80 to 85 | Statement: [Cataclysm, levelCapIncrease, 80 to 85]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelCapIncrease Context triple: [Cataclysm, levelCapIncrease, 80 to 85]
-
A.
raisedLevelCapFrom
Indicates that an entity has increased a previously existing maximum level limit from a specified lower value.
-
B.
raisesLevelCapTo
chosen
Indicates that one entity increases the maximum allowable level of another entity to a specified value.
-
C.
levelCapBefore
Indicates that one entity’s level limit or maximum allowable level must be reached or in place before the other entity’s level limit applies or can be attained.
-
D.
upgradeLevelCount
Indicates the number of upgrade levels that have been applied to, or are available for, an entity.
-
E.
raisesDevotionCapTo
Indicates increasing the maximum allowable level of devotion that an entity can have toward another entity or concept.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.