Triple
T4170886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-Story Weekly |
E84558
|
entity |
| Predicate | fictionType |
P22130
|
FINISHED |
| Object | genre fiction |
—
|
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: genre fiction | Statement: [All-Story Weekly, fictionType, genre fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionType Context triple: [All-Story Weekly, fictionType, genre fiction]
-
A.
fictionalMedium
Indicates that a work of fiction is presented or conveyed through a particular medium or format (such as a book, film, game, or comic).
-
B.
literaryGenreOfWork
chosen
Indicates that a work belongs to or is classified under a particular literary genre.
-
C.
fictionalMaterial
Indicates that something is made of, composed of, or incorporates a material that exists only in fiction or imagination.
-
D.
hasFictionComponent
Indicates that something includes, contains, or is composed in part of a fictional element or work.
-
E.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02c87cc88190a9ec3712db18a8a7 |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.