Triple

T32356129
Position Surface form Disambiguated ID Type / Status
Subject Pit Grave culture E826734 entity
Predicate geneticProfile P165790 FINISHED
Object high proportion of steppe ancestry 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: high proportion of steppe ancestry | Statement: [Pit Grave culture, geneticProfile, high proportion of steppe ancestry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: geneticProfile
Context triple: [Pit Grave culture, geneticProfile, high proportion of steppe ancestry]
  • A. geneticStatus
    Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
  • B. geneticFindings chosen
    Indicates that there is information describing observed genetic variants, mutations, or other genomic characteristics identified in an entity.
  • C. geneticOutcome
    Indicates the resulting genetic state or trait that arises from a specified genetic event, interaction, or condition.
  • D. geneticOrigin
    Indicates that one entity is the source or contributor of another entity’s genetic material or hereditary traits.
  • E. geneticInfluence
    Indicates that one entity affects or contributes to the genetic traits, characteristics, or heredity of another entity.
  • 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_69f34915a2588190bb3178f5ec2f48f4 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c1bb5f248190834161b5a6ba1ece completed May 3, 2026, 3:32 a.m.
PD Predicate disambiguation batch_69f6bd25bed08190befcabd3a41ffadf completed May 3, 2026, 3:12 a.m.
Created at: May 1, 2026, 12:49 a.m.