Triple
T30948151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bourne Initiative |
E788455
|
entity |
| Predicate | continuationOfWorkBy |
P120527
|
FINISHED |
| Object | Robert Ludlum |
—
|
NE NERFINISHED |
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: Robert Ludlum | Statement: [The Bourne Initiative, continuationOfWorkBy, Robert Ludlum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuationOfWorkBy Context triple: [The Bourne Initiative, continuationOfWorkBy, Robert Ludlum]
-
A.
continuesWorkBy
chosen
Indicates that one entity carries on, extends, or further develops the work previously initiated or performed by another entity.
-
B.
continuationWork
Indicates that one work continues, extends, or carries forward the content, narrative, or effort of another work.
-
C.
laterWorkBy
Indicates that one work was created after another work by the same creator or author.
-
D.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
E.
officeContinuedBy
Indicates that one office or term in a position is directly succeeded or carried on by another office or term.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 29, 2026, 8:53 p.m.