Triple
T10353651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Expectations |
E243942
|
entity |
| Predicate | placeInDickensOeuvre |
P19302
|
FINISHED |
| Object | one of Dickens's later novels |
—
|
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: one of Dickens's later novels | Statement: [Great Expectations, placeInDickensOeuvre, one of Dickens's later novels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInDickensOeuvre Context triple: [Great Expectations, placeInDickensOeuvre, one of Dickens's later novels]
-
A.
placeInApuleiusCorpus
Indicates that a given text or passage occurs within the works that make up the Apuleius corpus.
-
B.
positionInAuthorOeuvre
chosen
Indicates the relative placement or order of a work within an author's overall body of work.
-
C.
positionInFiction
Indicates that one entity holds a specific role, status, or placement within a fictional work or narrative.
-
D.
attestedInWorksOf
Indicates that something (such as a claim, form, or usage) is documented or evidenced within the works produced by a particular author or creator.
-
E.
literaryWorkInStory
Indicates that one literary work is referenced, featured, or embedded within the narrative of another story.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e952c878819084e5d7a593a3f9e9 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:58 a.m.