Triple
T5812911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Vause |
E128912
|
entity |
| Predicate | hasFlashbackStorylines |
P66473
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Alex Vause, hasFlashbackStorylines, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlashbackStorylines Context triple: [Alex Vause, hasFlashbackStorylines, yes]
-
A.
hasRevivalOrRelatedSeries
Indicates that an original work has a revival, reboot, continuation, or closely related follow-up series connected to it.
-
B.
hasAllyInStory
Indicates that one entity is portrayed as an ally or supportive partner of another entity within the context of a specific story or narrative.
-
C.
alternateTimelineVersionAppearsIn
Indicates that an alternate-timeline version of an entity appears or is present within a specified context, such as a work, scene, or universe.
-
D.
hasRevivalsIn
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
-
E.
hasFictionalShowWithinShow
Indicates that one show contains or features another fictional show within its 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b56044c8190847478a342d441c2 |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021d5ecd081908a62dd66e26f8598 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028ffe180819099e084fe557e789c |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:52 p.m.