Triple

T37460230
Position Surface form Disambiguated ID Type / Status
Subject Patchwerk E930898 entity
Predicate reintroducedLevelRange P188667 FINISHED
Object level 80 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 80 raid boss | Statement: [Patchwerk, reintroducedLevelRange, level 80 raid boss]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reintroducedLevelRange
Context triple: [Patchwerk, reintroducedLevelRange, level 80 raid boss]
  • A. reintroducedRange
    Indicates that an entity has been brought back or re-established within a specified geographic area after previously being absent or extirpated from that area.
  • B. reintroducedAsTier
    Indicates that something has been brought back or reinstated in a system or structure as a specific tier or level.
  • C. introducedRange
    Indicates that an entity has brought a particular range (such as a span, interval, or set of values) into existence, use, or consideration.
  • D. zoneLevelRangeAtLaunch
    Indicates the range of zone levels that apply at the moment something is launched or begins.
  • E. reintroducedFrom
    Indicates that an entity has been brought back or restored from a specified prior source, context, or location after having been removed, lost, or discontinued.
  • F. None of above. chosen

Provenance (4 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_69fbacaf54648190811ea33b34907e8e completed May 6, 2026, 9:03 p.m.
PD Predicate disambiguation batch_69fba883f770819091059c6f6c6af9f7 completed May 6, 2026, 8:45 p.m.
PDg Predicate description generation batch_69fbacaea12c8190a4c99e64335f0e7e completed May 6, 2026, 9:03 p.m.
Created at: May 3, 2026, 4:17 p.m.