Triple

T21839704
Position Surface form Disambiguated ID Type / Status
Subject Druella Black E539220 entity
Predicate hasFamilyTreeEntry P144770 FINISHED
Object Black family tapestry 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: Black family tapestry | Statement: [Druella Black, hasFamilyTreeEntry, Black family tapestry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFamilyTreeEntry
Context triple: [Druella Black, hasFamilyTreeEntry, Black family tapestry]
  • A. hasGenealogicalRelation
    Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
  • B. hasFamilyBranch
    Indicates that one entity is a subdivision, offshoot, or branch within the broader family group or lineage of another entity.
  • C. hasGenealogy chosen
    Indicates that one entity possesses or is associated with the genealogical record, lineage, or ancestry information of another entity.
  • D. hasFamilyRelationContext
    Indicates that there exists a family-based relationship or kinship context connecting the referenced entities.
  • E. hasDescendantPeople
    Indicates that one entity has other people as its descendants in a genealogical or lineage-based relationship.
  • 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_69e0c475cda88190987d08f23caebdc1 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f0a7aaa4f081909e869d2e81b07b91 completed April 28, 2026, 12:27 p.m.
PD Predicate disambiguation batch_69e6be8c14748190bdcc44a14d50bea4 completed April 21, 2026, 12:02 a.m.
Created at: April 16, 2026, 6:55 p.m.