Triple
T37716446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hot Stuff the Little Devil |
E939463
|
entity |
| Predicate | comicSeriesTitle |
P125284
|
FINISHED |
| Object | Hot Stuff, the Little Devil |
—
|
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: Hot Stuff, the Little Devil | Statement: [Hot Stuff the Little Devil, comicSeriesTitle, Hot Stuff, the Little Devil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comicSeriesTitle Context triple: [Hot Stuff the Little Devil, comicSeriesTitle, Hot Stuff, the Little Devil]
-
A.
comicTitle
chosen
Indicates that one entity is the title or name of a comic associated with another entity.
-
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.
appearsInSeriesByPublisher
Indicates that an entity appears in a series that is produced or released by a specified publisher.
-
D.
comicType
Indicates the specific category or format of a comic associated with an entity (e.g., strip, graphic novel, webcomic).
-
E.
hasComicSeries
Indicates that one entity is the comic series to which another entity belongs or with which it is associated.
- 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_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.