Triple

T34190370
Position Surface form Disambiguated ID Type / Status
Subject Roberto Zincone E877088 entity
Predicate maritalStatusWithMalinÅkerman P20884 FINISHED
Object divorced 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: divorced | Statement: [Roberto Zincone, maritalStatusWithMalinÅkerman, divorced]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maritalStatusWithMalinÅkerman
Context triple: [Roberto Zincone, maritalStatusWithMalinÅkerman, divorced]
  • A. maritalStatusInDisguise
    Indicates that an entity’s true marital status is being concealed or misrepresented, typically appearing different from what it actually is.
  • B. marital status chosen
    Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
  • C. maritalStatusClaimed
    Indicates that an entity has asserted or reported a particular marital status, regardless of whether it is verified or legally confirmed.
  • D. hasMaritalStatusAtEnd
    Indicates that an entity possesses a specific marital status at the end of a given period, event, or reference time.
  • E. maritalStatusInLegend
    Indicates the marital status attributed to an entity within a legend, myth, or traditional 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_69f349af20a4819089ac24d28f2d8112 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71362f1448190985a80ce7af475cb completed May 3, 2026, 9:20 a.m.
PD Predicate disambiguation batch_69f7127884388190884f23d181a65d19 completed May 3, 2026, 9:16 a.m.
Created at: May 1, 2026, 1:55 a.m.