Triple
T37550967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death Knight |
E933588
|
entity |
| Predicate | startingLevelAtRelease |
P187802
|
FINISHED |
| Object | 55 |
—
|
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: 55 | Statement: [Death Knight, startingLevelAtRelease, 55]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingLevelAtRelease Context triple: [Death Knight, startingLevelAtRelease, 55]
-
A.
recommendedLevelAtLaunch
chosen
Indicates the level that is advised or expected for an entity at the moment it is first introduced or made available.
-
B.
startingLevelRange
Indicates the range of initial levels at which an entity, activity, or state begins.
-
C.
initialReleaseFor
Indicates that one entity is the first or original release version associated with another entity (such as a work, product, or edition).
-
D.
intendedPlayerLevel
Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
-
E.
initialReleaseWith
Indicates that two or more entities were first released together as part of the same initial release event or package.
- 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_6a012594c27081908c80f0e0e6010290 |
completed | May 11, 2026, 12:40 a.m. |
| PD | Predicate disambiguation | batch_6a01252350548190b1df9edc9e581e91 |
completed | May 11, 2026, 12:38 a.m. |
Created at: May 3, 2026, 4:17 p.m.