Triple

T37718941
Position Surface form Disambiguated ID Type / Status
Subject Blue Diamond E939530 entity
Predicate hasSuperhumanPhysicalTraits P82757 FINISHED
Object yes LITERAL FINISHED

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: yes | Statement: [Blue Diamond, hasSuperhumanPhysicalTraits, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSuperhumanPhysicalTraits
Context triple: [Blue Diamond, hasSuperhumanPhysicalTraits, yes]
  • A. hasSuperpower
    Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
  • B. hasNoSuperhumanPowers
    Indicates that the subject lacks any abilities or powers beyond those of a normal human.
  • C. hasSuperheroMantle
    Indicates that one entity holds or has assumed the superhero identity, title, or role associated with another entity.
  • D. superhumanForm chosen
    Indicates that an entity has or assumes a form with abilities or attributes that exceed normal human limits.
  • E. notableTraitInMarvel
    Indicates that a particular trait or characteristic is especially prominent or noteworthy within the Marvel universe.
  • 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_69f76edc208c8190bc8b9683f75e1024 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a0067cde0f08190b2cd93af5f00d519 completed May 10, 2026, 11:11 a.m.
PD Predicate disambiguation batch_6a0065820c8c8190994734433c64a30a completed May 10, 2026, 11:01 a.m.
Created at: May 3, 2026, 4:18 p.m.