Triple

T32100773
Position Surface form Disambiguated ID Type / Status
Subject Ji E819841 entity
Predicate hasDescendantSurnames P36967 FINISHED
Object multiple later Chinese surnames derived from Zhou lineages 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 later Chinese surnames derived from Zhou lineages | Statement: [Ji, hasDescendantSurnames, multiple later Chinese surnames derived from Zhou lineages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDescendantSurnames
Context triple: [Ji, hasDescendantSurnames, multiple later Chinese surnames derived from Zhou lineages]
  • A. hasAncestralFamilyName
    Indicates that an entity bears or is associated with a family name inherited from its ancestors.
  • B. hasDescendantPeople
    Indicates that one entity has other people as its descendants in a genealogical or lineage-based relationship.
  • C. hasSeptSurname
    Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
  • D. hasComponentSurname
    Indicates that an entity’s full name includes a specified surname as one of its component parts.
  • E. hasBaseSurname chosen
    Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
  • 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_69f34901106881908ea893ad504a08be completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fe7eb4b8348190bb19d35766189ed4 completed May 9, 2026, 12:24 a.m.
PD Predicate disambiguation batch_69fe7c35d2148190ab952e54feda1e76 completed May 9, 2026, 12:13 a.m.
Created at: May 1, 2026, 12:26 a.m.