Triple

T22031541
Position Surface form Disambiguated ID Type / Status
Subject Southern Altai E544098 entity
Predicate anthropologicalType P138423 FINISHED
Object Siberian Turkic group 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: Siberian Turkic group | Statement: [Southern Altai, anthropologicalType, Siberian Turkic group]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: anthropologicalType
Context triple: [Southern Altai, anthropologicalType, Siberian Turkic group]
  • A. EthnicaType chosen
    Indicates a relationship where an entity is classified according to a specific ethnic category or type.
  • B. typeOfAncestry
    Indicates that one entity’s ancestry or lineage is characterized as being of a particular type or origin in relation to another entity.
  • C. anthropologicalSignificance
    Indicates that something holds importance or value for understanding human cultures, societies, or behaviors from an anthropological perspective.
  • D. allyType
    Indicates that one entity is classified as a specific type or category of ally in relation to another entity.
  • E. hasPopulationType
    Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
  • 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_69e11e2f98c8819083e11eab90942a78 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127edd5b48190a9aeb2840105c181 completed April 28, 2026, 9:34 p.m.
PD Predicate disambiguation batch_69e6f63b0d048190b241622759aab9de completed April 21, 2026, 3:59 a.m.
Created at: April 16, 2026, 8:24 p.m.