Triple

T25308247
Position Surface form Disambiguated ID Type / Status
Subject California Paid Family Leave program E634537 entity
Predicate coveredFamilyMember P158812 FINISHED
Object spouse 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: spouse | Statement: [California Paid Family Leave program, coveredFamilyMember, spouse]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coveredFamilyMember
Context triple: [California Paid Family Leave program, coveredFamilyMember, spouse]
  • A. coveredFamilyMember chosen
    Indicates that one person is included as an eligible dependent or beneficiary under another person’s insurance or benefit coverage.
  • B. closestLivingRelatives
    Indicates that the related entities are the most closely related to each other among all currently living entities, in terms of evolutionary or genealogical proximity.
  • C. uniqueFamilyMember
    Indicates that one entity is a family member of another in a way that is distinct and not shared by any other family member.
  • D. siblingOrRelative
    Indicates that two entities are related to each other by blood, marriage, or family ties, including but not limited to being siblings.
  • E. hasFamilialTieTo
    Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
  • 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_69e75a972c6481909bc11710e8d30a6c completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f55e519978819087a1676564a74630 completed May 2, 2026, 2:15 a.m.
PD Predicate disambiguation batch_69f4a0edd10c81908a052ab864d57c54 completed May 1, 2026, 12:47 p.m.
Created at: April 21, 2026, 1:25 p.m.