Triple

T38132355
Position Surface form Disambiguated ID Type / Status
Subject Nemesis Reborn E952257 entity
Predicate isReprofiledVersionOf P190256 FINISHED
Object Nemesis 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: Nemesis | Statement: [Nemesis Reborn, isReprofiledVersionOf, Nemesis]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isReprofiledVersionOf
Context triple: [Nemesis Reborn, isReprofiledVersionOf, Nemesis]
  • A. isSpecialVersionOf
    Indicates that one entity is a distinct or enhanced variant of another, typically differing by special features, configuration, or purpose while remaining fundamentally the same kind of thing.
  • B. isTemporaryVersionOf
    Indicates that one entity is a non-final, short-lived or provisional form of another, more permanent entity.
  • C. isVersionOf
    Indicates that one entity is a particular version, edition, or variant derived from another entity.
  • D. isInternalVersionOf
    Indicates that one entity is an internal or non-public variant, edition, or build of another entity.
  • E. isExternalVersionOf
    Indicates that one entity is a version or variant of another entity that exists or is maintained outside the primary or internal system or context.
  • 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_69f76f083548819082bd2bbf53c79e8e completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fcc42cbac48190b8d3e4c9ce140838 completed May 7, 2026, 4:56 p.m.
PD Predicate disambiguation batch_69fcb0fc69c88190800453eb57a7e62c completed May 7, 2026, 3:34 p.m.
PDg Predicate description generation batch_69fcc42b9334819099929649b7ef68ea completed May 7, 2026, 4:56 p.m.
Created at: May 3, 2026, 4:21 p.m.