Triple

T14391089
Position Surface form Disambiguated ID Type / Status
Subject Székelys E356842 entity
Predicate ethnogenesisDebate P114061 FINISHED
Object possible Turkic origins 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: possible Turkic origins | Statement: [Székelys, ethnogenesisDebate, possible Turkic origins]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ethnogenesisDebate
Context triple: [Székelys, ethnogenesisDebate, possible Turkic origins]
  • A. ethnogenesisOf
    Indicates the process or relationship by which a particular group, culture, or people comes into existence or forms its distinct identity.
  • B. ethnogenesisInCentury
    Indicates the century during which a particular ethnic group or people came into existence or was formed.
  • C. ethnogenesisRegion
    Indicates the geographic region where the formation or emergence of an ethnic group took place.
  • D. traditionalEthnogenesisPeriod
    Indicates the time span during which a group's ethnogenesis is traditionally understood to have occurred.
  • E. ethnicContinuityDebatedWith
    Indicates that there is scholarly or public debate over whether the ethnic identity or continuity between the related entities is historically or culturally valid.
  • 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_69d827927c988190ad98bb0360981783 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de902b9acc8190817ffa848a76a880 completed April 14, 2026, 7:06 p.m.
PD Predicate disambiguation batch_69de2aa024c48190805df6a9d63deb10 completed April 14, 2026, 11:53 a.m.
PDg Predicate description generation batch_69de2e08b6c08190bb4c929deab236a6 completed April 14, 2026, 12:07 p.m.
Created at: April 10, 2026, 1:16 a.m.