Triple

T27875529
Position Surface form Disambiguated ID Type / Status
Subject Joseph "Joe" Sullivan E704919 entity
Predicate heroicStatus P163247 FINISHED
Object heroic 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: heroic | Statement: [Joseph "Joe" Sullivan, heroicStatus, heroic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heroicStatus
Context triple: [Joseph "Joe" Sullivan, heroicStatus, heroic]
  • A. superheroStatus
    Indicates that an entity possesses the qualities, role, or designation of being a superhero, such as having heroic abilities, identity, or status.
  • B. heroClass
    Indicates the character class or role that a hero belongs to within a given system or context.
  • C. heroDepicted
    Indicates that one entity is portrayed or represented as a hero in relation to another entity.
  • D. heroPerformsFor
    Indicates that a hero carries out an action or performance for the benefit, entertainment, or service of another entity.
  • E. nativeHero
    Indicates that an entity is regarded as a heroic figure originating from or strongly associated with a particular place or community.
  • 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_69ef84111bb4819084298f994b31c62f completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69f6397f58a881908fdb9eb801175c27 completed May 2, 2026, 5:50 p.m.
PD Predicate disambiguation batch_69f6318be69481909d1bcf29b7b60eb2 completed May 2, 2026, 5:17 p.m.
PDg Predicate description generation batch_69f6352df6148190bc10772cd40bd7b3 completed May 2, 2026, 5:32 p.m.
Created at: April 27, 2026, 6:27 p.m.