Triple

T26170413
Position Surface form Disambiguated ID Type / Status
Subject Berserker (fix-up novel) E654384 entity
Predicate introducesFictionalUniverse P171399 FINISHED
Object Berserker universe 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: Berserker universe | Statement: [Berserker (fix-up novel), introducesFictionalUniverse, Berserker universe]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducesFictionalUniverse
Context triple: [Berserker (fix-up novel), introducesFictionalUniverse, Berserker universe]
  • A. fictionalUniverse
    Indicates that two entities exist within, or are associated with, the same fictional universe or narrative setting.
  • B. portraysFictionalUniverse
    Indicates that one entity depicts, represents, or presents the fictional universe in which another entity is set.
  • C. expandsFictionalUniverseOf
    Indicates that one work adds new content, details, or dimensions to the fictional universe established by another work.
  • D. hasFictionalUniverseProperty
    Indicates that a fictional universe possesses a specific characteristic, attribute, or property.
  • E. hasFictionalUniverseElement
    Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
  • 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_69ee5b44391c81908bdbd8813ba9aa99 completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f69f80b62c8190bf2af2be0d3a7df8 completed May 3, 2026, 1:06 a.m.
PD Predicate disambiguation batch_69f69d17e8d48190b30bcc2f4bd81eb2 completed May 3, 2026, 12:55 a.m.
PDg Predicate description generation batch_69f69edae2448190925ce701c8792c52 completed May 3, 2026, 1:03 a.m.
Created at: April 26, 2026, 8:35 p.m.