Triple
T37718611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Gabriele |
E939521
|
entity |
| Predicate | coCreatedCharacterFor |
P176002
|
FINISHED |
| Object | Timely Comics |
—
|
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: Timely Comics | Statement: [Al Gabriele, coCreatedCharacterFor, Timely Comics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coCreatedCharacterFor Context triple: [Al Gabriele, coCreatedCharacterFor, Timely Comics]
-
A.
coCreatedCharactersWith
Indicates that two or more entities jointly created one or more characters together.
-
B.
hasCreatedCharacterFor
chosen
Indicates that one entity has created or designed a character specifically for another entity or context.
-
C.
createdByCharacterRole
Indicates that something (such as a work, item, or event) was brought into existence or produced by an entity acting in a specific character role.
-
D.
creatorOfCharacter
Indicates that one entity is the originator or author who created or conceived the other entity as a character.
-
E.
franchiseCharacterCreator
Indicates that an entity is the creator or originator of a character that belongs to a particular franchise.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:18 p.m.