Triple
T22253822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelmorn |
E550046
|
entity |
| Predicate | settingGenreContext |
P78941
|
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: [Adelmorn, settingGenreContext, Gothic fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingGenreContext Context triple: [Adelmorn, settingGenreContext, Gothic fiction]
-
A.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
B.
genreContext
Indicates the contextual genre or categorical style associated with an entity, such as the thematic or stylistic framework in which it is situated.
-
C.
hasGenreAsSetting
chosen
Indicates that a work’s setting is characterized by, or takes place within, a particular genre.
-
D.
usedGenre
Indicates that one entity employs or is associated with a particular genre in its creation, presentation, or classification.
-
E.
isInGenreContext
Indicates that something occurs, is interpreted, or is relevant within the scope or framework of a particular genre.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138c0c4f48190a75473a7835014f1 |
completed | April 28, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:39 p.m.