Triple
T30848833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bourne Ascendancy |
E785718
|
entity |
| Predicate | characterRoleOfJasonBourne |
P23263
|
FINISHED |
| Object | amnesiac assassin |
—
|
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: amnesiac assassin | Statement: [The Bourne Ascendancy, characterRoleOfJasonBourne, amnesiac assassin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterRoleOfJasonBourne Context triple: [The Bourne Ascendancy, characterRoleOfJasonBourne, amnesiac assassin]
-
A.
characterPlayedByJasonStatham
Indicates that the subject is a character portrayed by the actor Jason Statham.
-
B.
leadActorForCharacter Buz Murdock
Indicates that the specified person is the primary actor portraying the character Buz Murdock.
-
C.
featuresCharacterRole
chosen
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
D.
filmCharacterDescribedAs
Indicates that a film character is described or characterized using a particular attribute, phrase, or depiction.
-
E.
John ClarkRole
Indicates that John holds or performs the role, position, or function specified by the associated entity or label.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: April 29, 2026, 8:46 p.m.