Triple
T13595074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tales to Astonish #27 |
E324796
|
entity |
| Predicate | featuresGenreStory |
P5483
|
FINISHED |
| Object | monster story |
—
|
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: monster story | Statement: [Tales to Astonish #27, featuresGenreStory, monster story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresGenreStory Context triple: [Tales to Astonish #27, featuresGenreStory, monster story]
-
A.
genreFeatures
chosen
Indicates that a particular genre is characterized or defined by certain features or attributes.
-
B.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
C.
genreWithin
Indicates that one genre is a subgenre or more specific category contained within another, broader genre.
-
D.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
E.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb057f1c881909a3bb77c659a724a |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.