Triple

T663905
Position Surface form Disambiguated ID Type / Status
Subject Sinte E12816 entity
Predicate ethnicContext P14216 FINISHED
Object European ethnic groups 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: European ethnic groups | Statement: [Sinte, ethnicContext, European ethnic groups]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ethnicContext
Context triple: [Sinte, ethnicContext, European ethnic groups]
  • A. ethnicCategoryIn chosen
    Indicates that an entity belongs to or is classified within a specified ethnic category in a given context.
  • B. culturalRegion
    Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
  • C. populationContext
    Indicates the demographic or population-related setting or conditions within which an entity, event, or measurement is defined or interpreted.
  • D. culturalVariation
    Indicates that there are differences in practices, beliefs, or expressions between cultures or within a culture across groups, contexts, or time.
  • E. positionOnCulture
    Indicates the stance, viewpoint, or opinion that one entity holds regarding cultural issues, practices, or phenomena in relation to another entity or context.
  • 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_69a493355dec819098d4244b2fa34885 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49fd1f0ec819087003d30bbab2fa6 completed March 1, 2026, 8:21 p.m.
PD Predicate disambiguation batch_69a49d16cff881908c8d2c3fe4d1d6fb completed March 1, 2026, 8:09 p.m.
Created at: March 1, 2026, 7:36 p.m.