Triple
T9965344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roderick Usher |
E195668
|
entity |
| Predicate | literaryThemeEmbodied |
P61759
|
FINISHED |
| Object | gothic horror |
—
|
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 horror | Statement: [Roderick Usher, literaryThemeEmbodied, gothic horror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryThemeEmbodied Context triple: [Roderick Usher, literaryThemeEmbodied, gothic horror]
-
A.
literaryThemeInvolvement
chosen
Indicates the involvement or presence of a particular literary theme within a work, passage, or character arc.
-
B.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
-
C.
literaryMuseOf
Indicates a relationship in which one entity serves as the creative inspiration or muse for another entity’s literary work.
-
D.
literaryScript
Indicates a relationship where an entity serves as the written text or script of a literary work, such as a play, film, or other narrative production.
-
E.
literaryFeature
Indicates a relationship where something possesses or exhibits a characteristic, device, or stylistic element used in literature.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb71c38488190a6f3cda11994f6a2 |
completed | April 2, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.