Triple

T27642179
Position Surface form Disambiguated ID Type / Status
Subject Nemesis (comic series) E696615 entity
Predicate creatorSharedUniverse P119254 FINISHED
Object Millarworld titles 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: Millarworld titles | Statement: [Nemesis (comic series), creatorSharedUniverse, Millarworld titles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: creatorSharedUniverse
Context triple: [Nemesis (comic series), creatorSharedUniverse, Millarworld titles]
  • A. createdInUniverseBy
    Indicates that something was brought into existence within a particular fictional or conceptual universe by a specific creator or originating agent.
  • B. associatedUniverse
    Indicates that one entity is linked or belongs to a particular universe, realm, or overarching world context.
  • C. creativeUniverseOwner
    Indicates that an entity holds ownership or authoritative control over a creative universe or fictional world.
  • D. sharesFictionalUniverseWith chosen
    Indicates that two entities are set within the same fictional universe or continuity, such that their stories coexist in a shared narrative world.
  • E. inUniverseMaker
    Indicates that an entity exists or occurs within the fictional universe created or defined by another entity.
  • 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_69ef5909f3848190805f35b76833e722 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f75dc25fa08190b371faf36d9fb72c completed May 3, 2026, 2:37 p.m.
PD Predicate disambiguation batch_69f758586534819083e91172f4bf5098 completed May 3, 2026, 2:14 p.m.
Created at: April 27, 2026, 2:27 p.m.