Triple
T32613674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadly Class |
E833726
|
entity |
| Predicate | comicCreators |
P86573
|
FINISHED |
| Object | Rick Remender |
—
|
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: Rick Remender | Statement: [Deadly Class, comicCreators, Rick Remender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comicCreators Context triple: [Deadly Class, comicCreators, Rick Remender]
-
A.
creatorInComics
chosen
Indicates that one entity is the creator (such as writer or artist) responsible for the content or characters appearing in a particular comic work or series.
-
B.
comicStripArtist
Indicates that one entity is the artist who creates or draws the comic strips associated with another entity.
-
C.
comicColorist
Indicates the relationship in which a person serves as the colorist for a comic, responsible for adding color to its artwork.
-
D.
creatorOfCharacter
Indicates that one entity is the originator or author who created or conceived the other entity as a character.
-
E.
coCreatedCharactersWith
Indicates that two or more entities jointly created one or more characters together.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:06 a.m.