Triple
T37550971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death Knight |
E933588
|
entity |
| Predicate | heroClassRequirement |
P188671
|
FINISHED |
| Object | requires high-level existing character at introduction |
—
|
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: requires high-level existing character at introduction | Statement: [Death Knight, heroClassRequirement, requires high-level existing character at introduction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroClassRequirement Context triple: [Death Knight, heroClassRequirement, requires high-level existing character at introduction]
-
A.
heroClassRestriction
chosen
Indicates that a particular action, item, or ability is restricted to heroes of specific classes or class types.
-
B.
heroClass
Indicates the character class or role that a hero belongs to within a given system or context.
-
C.
levelRequirement
Indicates that one entity specifies the minimum level or threshold another entity must meet in order for an action, access, or condition to be valid.
-
D.
heroicLevel
Indicates the degree or extent to which an entity exhibits heroism or heroic qualities.
-
E.
requiresSkill
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.