Triple

T15074853
Position Surface form Disambiguated ID Type / Status
Subject 4 the Cause E379971 entity
Predicate familyRelationBetweenMembers P89441 FINISHED
Object Edwards siblings 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: Edwards siblings | Statement: [4 the Cause, familyRelationBetweenMembers, Edwards siblings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: familyRelationBetweenMembers
Context triple: [4 the Cause, familyRelationBetweenMembers, Edwards siblings]
  • A. familyConnectionTo chosen
    Indicates a familial relationship or bond that exists between two entities, such as by blood, marriage, or adoption.
  • B. familyRelationNote
    Indicates a descriptive note or annotation that provides additional context or clarification about a specified family relationship between entities.
  • C. familyOf
    Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
  • D. relationshipToRelative
    Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
  • E. basisOfRelationship
    Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
  • 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_69d85cd7683881908d405c1b5d7b4f7f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69dff7fb60448190b454386dd762644d completed April 15, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69deb95a182081908fffc4402b02a394 completed April 14, 2026, 10:02 p.m.
Created at: April 10, 2026, 3:02 a.m.