Triple

T33564711
Position Surface form Disambiguated ID Type / Status
Subject Pictet E859724 entity
Predicate hasGenealogicalType P193375 FINISHED
Object hereditary family name 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: hereditary family name | Statement: [Pictet, hasGenealogicalType, hereditary family name]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGenealogicalType
Context triple: [Pictet, hasGenealogicalType, hereditary family name]
  • A. hasGenealogy
    Indicates that one entity possesses or is associated with the genealogical record, lineage, or ancestry information of another entity.
  • B. hasGenealogicalRelation
    Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
  • C. hasGenealogicalInterest
    Indicates a relationship in which one entity has a research, documentation, or personal interest in the family history or lineage of another entity.
  • D. hasGenealogicalSignificance
    Indicates that something holds importance or relevance within a genealogical or family-lineage context.
  • E. genealogicalClassification
    Indicates a relationship where one entity is categorized within a family or lineage structure relative to another, based on genealogical or ancestral connections.
  • 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_69f3497c1d288190a844ea699914e038 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fd44474ed48190ac372e4c88d762ed completed May 8, 2026, 2:02 a.m.
PD Predicate disambiguation batch_69fd41ef28a48190a66959be5c964461 completed May 8, 2026, 1:52 a.m.
PDg Predicate description generation batch_69fd4445f8c08190bb2dc27e0971c55d completed May 8, 2026, 2:02 a.m.
Created at: May 1, 2026, 1:40 a.m.