Triple

T32356130
Position Surface form Disambiguated ID Type / Status
Subject Pit Grave culture E826734 entity
Predicate YChromosomeHaplogroup P174180 FINISHED
Object R1b-M269 (frequent) 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: R1b-M269 (frequent) | Statement: [Pit Grave culture, YChromosomeHaplogroup, R1b-M269 (frequent)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: YChromosomeHaplogroup
Context triple: [Pit Grave culture, YChromosomeHaplogroup, R1b-M269 (frequent)]
  • A. mtHaplogroup
    Indicates that one entity is classified as having a specific mitochondrial DNA haplogroup associated with the other entity.
  • B. ancestralSubgroups
    Indicates that one group consists of or descends from earlier, foundational subgroups within a lineage or hierarchy.
  • C. ancestralGroup
    Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
  • D. genealogicalClassification
    Indicates a relationship where one entity is categorized within a family or lineage structure relative to another, based on genealogical or ancestral connections.
  • E. geneticOrigin
    Indicates that one entity is the source or contributor of another entity’s genetic material or hereditary traits.
  • 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_69f34915a2588190bb3178f5ec2f48f4 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6be602eec8190961d92f4db7d94a7 completed May 3, 2026, 3:17 a.m.
PD Predicate disambiguation batch_69f6ba6cef208190bc5cd43d96127004 completed May 3, 2026, 3:01 a.m.
PDg Predicate description generation batch_69f6bbbe23d48190b2aa662d69b41900 completed May 3, 2026, 3:06 a.m.
Created at: May 1, 2026, 12:49 a.m.