Triple

T27642065
Position Surface form Disambiguated ID Type / Status
Subject Superior E696613 entity
Predicate fictionalSuperheroIdentity P86336 FINISHED
Object Superior (in-universe superhero) 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: Superior (in-universe superhero) | Statement: [Superior, fictionalSuperheroIdentity, Superior (in-universe superhero)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fictionalSuperheroIdentity
Context triple: [Superior, fictionalSuperheroIdentity, Superior (in-universe superhero)]
  • A. usedBySuperheroIdentity
    Indicates that a particular item, tool, or resource is utilized by a given superhero identity.
  • B. hasFictionalAlterEgoOf chosen
    Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
  • C. associatedWithSuperheroIdentity
    Indicates that an entity has a connection or linkage to a particular superhero identity, such as being or representing that superhero persona.
  • D. hasSuperheroIdentityType
    Indicates the type or category of a superhero identity associated with an entity (e.g., secret, public, dual).
  • E. usesSuperheroIdentity
    Indicates that an entity adopts or operates under a superhero persona or alias, rather than their ordinary identity.
  • 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_69f6fb19063c81909466b329655c8583 completed May 3, 2026, 7:36 a.m.
PD Predicate disambiguation batch_69f6f969b4cc8190afb473a2d8b110bc completed May 3, 2026, 7:29 a.m.
Created at: April 27, 2026, 2:27 p.m.