Triple
T35708658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conte fantastique |
E1031789
|
entity |
| Predicate | associatedLiteraryGenre |
P22130
|
FINISHED |
| Object | Gothic 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: Gothic fiction | Statement: [Conte fantastique, associatedLiteraryGenre, Gothic fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLiteraryGenre Context triple: [Conte fantastique, associatedLiteraryGenre, Gothic fiction]
-
A.
literaryGenreAssociated
Indicates that there is an association between an entity and a particular literary genre with which it is related or classified.
-
B.
literaryGenreOfWork
chosen
Indicates that a work belongs to or is classified under a particular literary genre.
-
C.
literaryGenreOfWorkAppearedIn
Indicates the literary genre of the work in which a given entity (such as a text, character, or element) appears.
-
D.
literaryGenreOfSourceWork
Indicates that a work belongs to, or is characterized by, a particular literary genre.
-
E.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.