Triple
T33591887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Drake |
E860446
|
entity |
| Predicate | replacesProtagonistOf |
P98140
|
FINISHED |
| Object | Sam Tyler |
—
|
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: Sam Tyler | Statement: [Alex Drake, replacesProtagonistOf, Sam Tyler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesProtagonistOf Context triple: [Alex Drake, replacesProtagonistOf, Sam Tyler]
-
A.
replacesCharacterInRole
chosen
Indicates that one character takes over and performs the same role previously held by another character.
-
B.
actsInSteadOf
Indicates that one entity performs an action or fulfills a role as a substitute or proxy for another entity.
-
C.
replacedByInFilmAdaptation
Indicates that in a film adaptation, one entity (such as a character, object, or element) is substituted or superseded by another entity fulfilling a similar role.
-
D.
protagonistAlterEgoOf
Indicates that one entity is the alternate identity or secret persona of the main character (protagonist) in a narrative.
-
E.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 1, 2026, 1:40 a.m.