Triple

T32176537
Position Surface form Disambiguated ID Type / Status
Subject Paul Stadler E821863 entity
Predicate maritalStatusWithJoWilson P163910 FINISHED
Object abusive marriage 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: abusive marriage | Statement: [Paul Stadler, maritalStatusWithJoWilson, abusive marriage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maritalStatusWithJoWilson
Context triple: [Paul Stadler, maritalStatusWithJoWilson, abusive marriage]
  • A. marital status
    Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
  • B. maritalStatusOfUnion chosen
    Indicates the type or state of the marital relationship that characterizes a particular union between entities.
  • C. maritalStatusInDisguise
    Indicates that an entity’s true marital status is being concealed or misrepresented, typically appearing different from what it actually is.
  • D. marriedBy
    Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
  • E. maritalStatusClaimed
    Indicates that an entity has asserted or reported a particular marital status, regardless of whether it is verified or legally confirmed.
  • 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_69f3490755288190aee11740a34862f9 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c8159edc8190b1c87015e0c820e8 completed May 3, 2026, 3:59 a.m.
PD Predicate disambiguation batch_69f6c3f42fbc8190a06eb1044c9e6094 completed May 3, 2026, 3:41 a.m.
Created at: May 1, 2026, 12:34 a.m.