Triple

T11252110
Position Surface form Disambiguated ID Type / Status
Subject The Evil Within E266342 entity
Predicate difficultyModes P98721 FINISHED
Object multiple difficulty levels 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: multiple difficulty levels | Statement: [The Evil Within, difficultyModes, multiple difficulty levels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: difficultyModes
Context triple: [The Evil Within, difficultyModes, multiple difficulty levels]
  • A. difficultySource
    Indicates that one entity is the cause, origin, or contributing factor to the difficulty or challenge experienced in relation to another entity or situation.
  • B. difficulty
    Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
  • C. difficultySystem
    Indicates a relationship where a system is characterized or classified by its level of difficulty.
  • D. difficultyClassRange
    Indicates the range of difficulty classes within which an action, task, or challenge is considered to fall.
  • E. difficultyRelativeTo
    Indicates that one entity’s level of difficulty is being compared to and expressed in relation to another entity’s level of difficulty.
  • 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_69d6aac7953c8190b82caf9d7640fdf9 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e933648481909873094bc89ed041 completed April 9, 2026, 6 p.m.
PD Predicate disambiguation batch_69d78793c00481908a3f764b610b77a4 completed April 9, 2026, 11:03 a.m.
PDg Predicate description generation batch_69d796cf74308190a5b29d0dd82954a2 completed April 9, 2026, 12:08 p.m.
Created at: April 8, 2026, 9:31 p.m.