Triple

T37730517
Position Surface form Disambiguated ID Type / Status
Subject Kill or Be Killed (Image Comics series) E940139 entity
Predicate createdByTeam P201432 FINISHED
Object Ed Brubaker and Sean Phillips 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: Ed Brubaker and Sean Phillips | Statement: [Kill or Be Killed (Image Comics series), createdByTeam, Ed Brubaker and Sean Phillips]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: createdByTeam
Context triple: [Kill or Be Killed (Image Comics series), createdByTeam, Ed Brubaker and Sean Phillips]
  • A. wroteTeam
    Indicates that an entity authored or co-authored a work on behalf of, or as a member of, a specific team.
  • B. usedByTeam
    Indicates that something (such as a resource, tool, or method) is utilized or employed by a particular team.
  • C. managedTeamFrom
    Indicates that one entity led, directed, or supervised a team originating from or based in another specified entity.
  • D. createdByDivision
    Indicates that something was produced, established, or brought into existence by a specific division within an organization.
  • E. managedTeam
    Indicates that one entity had responsibility for directing, supervising, and coordinating the work of another group or team.
  • 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_69f76edefd048190a32212c5c3919531 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fff4530f908190afe9387f732c2b7e completed May 10, 2026, 2:58 a.m.
PD Predicate disambiguation batch_69fff3c01a64819091196875b0c88607 completed May 10, 2026, 2:56 a.m.
PDg Predicate description generation batch_69fff4525ce48190b1d760539e68aadc completed May 10, 2026, 2:58 a.m.
Created at: May 3, 2026, 4:18 p.m.