Triple

T696445
Position Surface form Disambiguated ID Type / Status
Subject Ashkenazi Jewish diaspora E13903 entity
Predicate sharesAncestralOriginWith P1969 FINISHED
Object other Jewish communities 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: other Jewish communities | Statement: [Ashkenazi Jewish diaspora, sharesAncestralOriginWith, other Jewish communities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sharesAncestralOriginWith
Context triple: [Ashkenazi Jewish diaspora, sharesAncestralOriginWith, other Jewish communities]
  • A. hasLastNameInCommonWith
    Indicates that two entities share the same last name.
  • B. sharesDNAWithHumans
    Indicates that one entity possesses genetic material that is evolutionarily related to, and partially identical with, that of humans.
  • C. foundingAncestor
    Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
  • D. relatedEthnicGroup chosen
    Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
  • E. hasFamilialTieTo
    Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
  • 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_69a493406c408190957eeec9048a8fb6 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a0c8055881909565ebde2be8fd7a completed March 1, 2026, 8:25 p.m.
PD Predicate disambiguation batch_69a49d23e0a08190b08be9d1eff2a1bb completed March 1, 2026, 8:10 p.m.
Created at: March 1, 2026, 7:36 p.m.