Triple
T31026265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bourne Evolution |
E790580
|
entity |
| Predicate | seriesContinuationAfter |
P118951
|
FINISHED |
| Object | earlier Jason Bourne 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: earlier Jason Bourne novels | Statement: [The Bourne Evolution, seriesContinuationAfter, earlier Jason Bourne novels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesContinuationAfter Context triple: [The Bourne Evolution, seriesContinuationAfter, earlier Jason Bourne novels]
-
A.
seriesContinuity
Indicates that one work, episode, or installment maintains narrative or canonical continuity with another within the same series.
-
B.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
C.
seriesNumberInCarryOn
Indicates that an item has a specific series or sequence number within a set of carry-on items.
-
D.
laterSeriesName
chosen
Indicates that one series is a subsequent or later-titled continuation or successor of another series.
-
E.
continuesOn
Indicates that an action, process, or state persists or carries forward beyond a given point, without interruption or termination.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 8:58 p.m.