Triple
T29025801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tales to Astonish |
E737588
|
entity |
| Predicate | comicBookType |
P139288
|
FINISHED |
| Object | anthology series |
—
|
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: anthology series | Statement: [Tales to Astonish, comicBookType, anthology series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comicBookType Context triple: [Tales to Astonish, comicBookType, anthology series]
-
A.
comicType
chosen
Indicates the specific category or format of a comic associated with an entity (e.g., strip, graphic novel, webcomic).
-
B.
comicBookUniverse
Indicates that multiple comic book characters, stories, or events exist within and are governed by the same fictional continuity or shared narrative world.
-
C.
comicTitle
Indicates that one entity is the title or name of a comic associated with another entity.
-
D.
comicFunction
Indicates a relationship where something serves a humorous or entertainment role, such as providing comedy, comic relief, or a joking purpose within a context.
-
E.
comicPublisher
Indicates that one entity is the publisher responsible for producing or distributing the comic associated with another entity.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 9:52 a.m.