Triple

T18208466
Position Surface form Disambiguated ID Type / Status
Subject Lamproba E435966 entity
Predicate instanceOf P0 FINISHED
Object Svan cultural tradition C2736 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: Svan cultural tradition
Context triple: [Lamproba, instanceOf, Svan cultural tradition]
  • A. Ossetian cultural tradition
    Ossetian cultural tradition encompasses the customs, rituals, language, folklore, and social practices of the Ossetian people, shaped by their Caucasian heritage, Iranian roots, and Orthodox Christian and folk religious influences.
  • B. Nordic tradition
    Nordic tradition encompasses the customs, beliefs, rituals, and cultural practices that have developed over centuries in the Nordic countries, shaped by their history, mythology, climate, and social values.
  • C. Georgian cultural tradition chosen
    Georgian cultural tradition encompasses the rich tapestry of customs, rituals, music, dance, cuisine, and social values that have evolved in Georgia over centuries, reflecting its unique blend of indigenous practices and influences from neighboring civilizations.
  • D. Arctic cultural tradition
    Arctic cultural tradition encompasses the beliefs, practices, arts, and social customs developed by Indigenous peoples of the circumpolar North in close relationship with extreme cold environments, seasonal cycles, and subsistence lifeways.
  • E. Sardinian culture
    Sardinian culture is the distinctive blend of ancient Nuragic heritage, pastoral traditions, unique Romance language variants, and rich music, food, and festival customs that characterize the island of Sardinia and its people.
  • F. None of above.

Provenance (1 batch)

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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
Created at: April 10, 2026, 10:32 a.m.