Triple
T9875104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pechenegs |
E240053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval ethnic group |
C352
|
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: medieval ethnic group Context triple: [Pechenegs, instanceOf, medieval ethnic group]
-
A.
group of medieval polities
A group of medieval polities is a collection of semi-autonomous kingdoms, principalities, city-states, or other territorial entities that interacted through shifting alliances, conflicts, and hierarchies within the broader sociopolitical landscape of the Middle Ages.
-
B.
ethnic group
chosen
An ethnic group is a social category of people who identify with each other based on shared ancestry, culture, language, history, and often a common geographic origin.
-
C.
medieval people
Medieval people are individuals living during the Middle Ages, typically characterized by feudal social structures, agrarian lifestyles, religious centrality, and limited technological development compared to later periods.
-
D.
legendary population group
A legendary population group is a community or people described in myths, folklore, or historical legends whose existence, characteristics, or deeds are exaggerated, symbolic, or not fully supported by empirical evidence.
-
E.
historical group
A historical group is a collection of people connected by a shared identity, purpose, or activity that existed and acted within a specific past time period.
- 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_69ca84e8a0788190b9061811d50fd554 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:37 p.m.