Triple

T38478069
Position Surface form Disambiguated ID Type / Status
Subject Knee-Deep in the Dead E915598 entity
Predicate difficultySettings P2406 FINISHED
Object I’m Too Young to Die NE NERFINISHED

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: I’m Too Young to Die | Statement: [Knee-Deep in the Dead, difficultySettings, I’m Too Young to Die]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: difficultySettings
Context triple: [Knee-Deep in the Dead, difficultySettings, I’m Too Young to Die]
  • A. difficultyOption
    Indicates a relationship where a particular option specifies or represents a level of difficulty for something (e.g., a task, question, or activity).
  • B. difficultyModes
    Indicates the different levels of challenge or complexity available for performing a task, activity, or process.
  • C. difficultyStage
    Indicates the difficulty level or phase associated with a particular task, process, or item.
  • D. difficulty chosen
    Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
  • E. 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.
  • 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_69f76e8ff5cc8190a88803369183845e completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fcec5f8b448190b48330a19b462d24 completed May 7, 2026, 7:47 p.m.
PD Predicate disambiguation batch_69fceaf1e23881908ca24160a638e329 completed May 7, 2026, 7:41 p.m.
Created at: May 3, 2026, 4:31 p.m.