Triple
T9691466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Last Years |
E234545
|
entity |
| Predicate | workInSeriesAfter |
P88827
|
FINISHED |
| Object | Other volumes of The Life of Klim Samgin |
—
|
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: Other volumes of The Life of Klim Samgin | Statement: [The Last Years, workInSeriesAfter, Other volumes of The Life of Klim Samgin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workInSeriesAfter Context triple: [The Last Years, workInSeriesAfter, Other volumes of The Life of Klim Samgin]
-
A.
sequenceInWork
Indicates that one work appears as a sequential part or installment within a larger overarching work.
-
B.
hasWorkInSeriesRole
Indicates that an entity holds a specific role or function within a particular work that is part of a series.
-
C.
finalWorkInSeries
Indicates that one work is the concluding or last installment within a series of related works.
-
D.
nextInSeries
chosen
Indicates that one entity directly follows another in an ordered sequence or progression.
-
E.
laterWorkBy
Indicates that one work was created after another work by the same creator or author.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d0422e88190a234ba74eb0dad25 |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.