Triple

T23059557
Position Surface form Disambiguated ID Type / Status
Subject Violet Venable E574257 entity
Predicate seeksToControl P69335 FINISHED
Object the narrative of Sebastian Venable's life 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: the narrative of Sebastian Venable's life | Statement: [Violet Venable, seeksToControl, the narrative of Sebastian Venable's life]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: seeksToControl
Context triple: [Violet Venable, seeksToControl, the narrative of Sebastian Venable's life]
  • A. endedControlOf
    Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
  • B. aimsToControl chosen
    Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
  • C. continuesToControl
    Indicates that one entity maintains ongoing authority, influence, or command over another entity or resource over time.
  • D. canBeControlledFrom
    Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
  • E. usedToControl
    Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
  • 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_69e245ba7ae48190be606dbc54120e39 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1899f359081909e89e19db3833a3d completed April 29, 2026, 4:31 a.m.
PD Predicate disambiguation batch_69ef89d5f71881908b9f9d0c8aab278c completed April 27, 2026, 4:07 p.m.
Created at: April 17, 2026, 3:55 p.m.