Triple

T32945903
Position Surface form Disambiguated ID Type / Status
Subject Jenna Hunterson E842798 entity
Predicate resolvesArcBy P172650 FINISHED
Object deciding to raise her daughter on her own 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: deciding to raise her daughter on her own | Statement: [Jenna Hunterson, resolvesArcBy, deciding to raise her daughter on her own]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: resolvesArcBy
Context triple: [Jenna Hunterson, resolvesArcBy, deciding to raise her daughter on her own]
  • A. resolutionOfArc
    Indicates the degree of detail or fineness with which an arc is represented or approximated in a geometric or graphical context.
  • B. resolutionArc chosen
    Indicates the narrative process or sequence of events through which a conflict, tension, or problem is brought to a conclusion or resolved.
  • C. undergoesArc
    Indicates that an entity is subjected to or experiences a specific arc process, transformation, or phase.
  • D. hasArc
    Indicates that there is a directed connection or edge from one entity to another, often representing a link in a graph or network.
  • E. formsArcOf
    Indicates that one entity curves around or spans between points so as to create an arc in relation to another entity.
  • 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_69f34949727c81909d195c97de3341c8 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d14056688190a07663ccfbbc4086 completed May 3, 2026, 4:38 a.m.
PD Predicate disambiguation batch_69f6cfe5f93c8190995c53dbbe380a32 completed May 3, 2026, 4:32 a.m.
Created at: May 1, 2026, 1:20 a.m.