Triple
T37460229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patchwerk |
E930898
|
entity |
| Predicate | originalLevelRange |
P203098
|
FINISHED |
| Object | level 60 raid boss |
—
|
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: level 60 raid boss | Statement: [Patchwerk, originalLevelRange, level 60 raid boss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalLevelRange Context triple: [Patchwerk, originalLevelRange, level 60 raid boss]
-
A.
yLevelRange
Indicates that one entity’s vertical position or height falls within a specified range relative to another entity or reference level.
-
B.
startingLevelRange
chosen
Indicates the range of initial levels at which an entity, activity, or state begins.
-
C.
reintroducedLevelRange
Indicates that an entity has been reintroduced within a specified range or interval of levels.
-
D.
zoneLevelRange
Indicates the range of zone levels within which a given condition, rule, or classification applies.
-
E.
requiresLevelRange
Indicates that something is only applicable, accessible, or valid for entities whose level falls within a specified minimum-to-maximum range.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.