Triple
T37718235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-Star Comics (revival) |
E939510
|
entity |
| Predicate | hasCreativeSupervisor |
P184400
|
FINISHED |
| Object | Roy Thomas |
—
|
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: Roy Thomas | Statement: [All-Star Comics (revival), hasCreativeSupervisor, Roy Thomas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreativeSupervisor Context triple: [All-Star Comics (revival), hasCreativeSupervisor, Roy Thomas]
-
A.
hasCreativeDirectorRoleAt
Indicates that an entity holds the position or responsibilities of a creative director at a specified organization or project.
-
B.
hasCreativeLeader
Indicates that an entity is led or directed in its creative aspects by a specific person or organization.
-
C.
hasDirectorCreator
Indicates that an entity has a person or organization who directed or created it (e.g., a film’s director or a work’s creator).
-
D.
hasCreativeControl
chosen
Indicates that one entity possesses the authority to make final decisions over the creation, direction, or modification of another entity’s content or form.
-
E.
hasArtDirector
Indicates that an entity has a specific person or organization serving as its art director.
- 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_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:18 p.m.