Triple
T10353618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Expectations |
E243942
|
entity |
| Predicate | firstPublicationEndDate |
P29318
|
FINISHED |
| Object | 1861-08-03 |
—
|
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: 1861-08-03 | Statement: [Great Expectations, firstPublicationEndDate, 1861-08-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPublicationEndDate Context triple: [Great Expectations, firstPublicationEndDate, 1861-08-03]
-
A.
finalPublicationDate
Indicates the date on which a work is officially and definitively published in its final form.
-
B.
firstPublicationPeriod
chosen
Indicates the time span during which something was first published or initially made publicly available.
-
C.
lastPublicationYear
Indicates the year in which an entity’s most recent publication was released.
-
D.
initialProductionEndDate
Indicates the date on which the initial phase or run of production for something comes to an end.
-
E.
serializationEndYear
Indicates the year in which the serialization or serialized publication of an entity concluded.
- 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.