Triple
T10380144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bourne Ascendancy |
E244615
|
entity |
| Predicate | hasProtagonistCondition |
P93885
|
FINISHED |
| Object | amnesiac |
—
|
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 | Statement: [The Bourne Ascendancy, hasProtagonistCondition, amnesiac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistCondition Context triple: [The Bourne Ascendancy, hasProtagonistCondition, amnesiac]
-
A.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
hasProtagonistAbility
Indicates that a protagonist possesses a specific ability, power, or special skill.
-
C.
hasInspectorProtagonist
Indicates that the main character in the work serves in the role of an inspector.
-
D.
hasPrisonerCondition
Indicates that a specified prisoner is subject to a particular condition, status, or restriction within a custodial or correctional context.
-
E.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
- F. None of above. chosen
Provenance (4 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e991056c8190a981f717c51f1f72 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:03 p.m.