Triple
T37553999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shazzrah |
E933650
|
entity |
| Predicate | designedForLevelRange |
P100059
|
FINISHED |
| Object | 60 |
—
|
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: 60 | Statement: [Shazzrah, designedForLevelRange, 60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForLevelRange Context triple: [Shazzrah, designedForLevelRange, 60]
-
A.
designedForLevelCap
Indicates that something is specifically created or configured to be suitable for use at a particular maximum level or level cap.
-
B.
intendedPlayerLevel
chosen
Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
-
C.
combatLevelRange
Indicates the range of combat levels within which two entities can validly or effectively engage in combat with each other.
-
D.
recommendedLevelRangeRetail
Indicates the range of levels at which a product is recommended to be sold or used in a retail context.
-
E.
eligibilityGradeLevel
Indicates the grade level or range of grade levels for which an entity is considered eligible or appropriate.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
Created at: May 3, 2026, 4:17 p.m.