Triple

T35233450
Position Surface form Disambiguated ID Type / Status
Subject Sousa E1017304 entity
Predicate hasPatronymicLineages P200966 FINISHED
Object multiple unrelated Sousa families 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: multiple unrelated Sousa families | Statement: [Sousa, hasPatronymicLineages, multiple unrelated Sousa families]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPatronymicLineages
Context triple: [Sousa, hasPatronymicLineages, multiple unrelated Sousa families]
  • A. hasPatronymicLine
    Indicates a genealogical relationship where one entity’s name or lineage is derived from the father’s given name, forming a patronymic line.
  • B. isPatronymicOrFamilyBased
    Indicates that one entity’s name is derived from or based on the personal or family name of another entity.
  • C. hasPatronymicDerivative
    Indicates that one name or term is derived from another by forming a patronymic, typically expressing descent or lineage from a person.
  • D. hasPatronymicUse
    Indicates that an entity uses a patronymic form of naming derived from a parent’s (typically the father’s) given name.
  • E. isPatronymicSurname
    Indicates that a surname is derived from the given name of a father or male ancestor, typically signifying "son/daughter of" that person.
  • F. None of above. chosen

Provenance (4 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_69f76de12e4c8190bc46b71a32858356 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69ffbe9e47688190a2692566dc326646 completed May 9, 2026, 11:09 p.m.
PD Predicate disambiguation batch_69ffbb7b45388190b62cbde5c2d435cd completed May 9, 2026, 10:55 p.m.
PDg Predicate description generation batch_69ffbe9c7c348190b6b72455d6a3e3d8 completed May 9, 2026, 11:09 p.m.
Created at: May 3, 2026, 4:02 p.m.