Triple
T10353610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Expectations |
E243942
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Victorian literature work |
C4035
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Victorian literature work Context triple: [Great Expectations, instanceOf, Victorian literature work]
-
A.
English Renaissance literature work
An English Renaissance literature work is a text—such as a poem, play, or prose narrative—produced in England roughly between the late 15th and early 17th centuries, characterized by humanist themes, experimentation with form, and a revitalized interest in classical antiquity.
-
B.
literaryWork
chosen
A literaryWork is a created written or spoken artistic composition, such as a novel, poem, or play, that conveys ideas, stories, or emotions through language.
-
C.
Scottish literary work
A Scottish literary work is a piece of writing—such as a novel, poem, play, or essay—created by a Scottish author or strongly rooted in Scotland’s culture, history, language, or landscape.
-
D.
medieval literary work
A medieval literary work is a written or orally transmitted text from roughly the 5th to the 15th century that reflects the cultural, religious, and social contexts of the Middle Ages through genres such as epics, romances, hagiographies, chronicles, and lyric poetry.
-
E.
Victorian novel cycle
A Victorian novel cycle is a series of interrelated novels, typically published over time in 19th-century Britain, that share a common setting, characters, or overarching narrative to create a larger, unified fictional world.
- F. None of above.
Provenance (1 batch)
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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:58 a.m.