Triple
T19754290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Weird |
E474463
|
entity |
| Predicate | isRelatedToGenre |
P122929
|
FINISHED |
| Object | weird 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: weird fiction | Statement: [New Weird, isRelatedToGenre, weird fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelatedToGenre Context triple: [New Weird, isRelatedToGenre, weird fiction]
-
A.
hasGenreRelation
Indicates that there is an association between an entity and a specific genre, specifying the type or category it belongs to.
-
B.
isAssociatedWithSubgenre
Indicates that one entity has a connection or linkage to a specific subgenre of a broader category.
-
C.
genreRelation
chosen
Indicates a relationship where one entity is categorized as having, belonging to, or being associated with a particular genre defined by another entity.
-
D.
associatedWithGenreElement
Indicates that something has a connection or linkage to a specific genre-related element (such as a motif, convention, or stylistic feature).
-
E.
hasGenreInRoles
Indicates that an entity participates in roles associated with a particular genre or set of genres.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6529dada081909c5b4d65247c6032 |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.