Triple
T31639897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suomar |
E807418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Alemannic war leader |
C7709
|
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: Alemannic war leader Context triple: [Suomar, instanceOf, Alemannic war leader]
-
A.
Germanic ruler
chosen
A Germanic ruler is a sovereign or chieftain from one of the Germanic peoples who exercised political, military, and often religious authority over a tribe, kingdom, or territory in Europe.
-
B.
Arvernian ruler
An Arvernian ruler is the sovereign leader of the ancient Arvernian people, responsible for governing their territory, commanding their armies, managing alliances and rivalries with neighboring tribes and Rome, and upholding the cultural and religious traditions of their society.
-
C.
Viking leader
A Viking leader is a powerful and charismatic figure who commands warriors, plans raids and explorations, and upholds the laws, honor, and prosperity of their Norse community.
-
D.
Gallic chieftain
A Gallic chieftain is the tribal leader of an ancient Celtic community in Gaul, responsible for military command, political decision-making, and the maintenance of social order and alliances.
-
E.
Bavarian military officer
A Bavarian military officer is a commissioned leader from the historical Kingdom or modern state of Bavaria, responsible for commanding troops, executing military strategy, and upholding regional and national defense duties within the broader German armed forces context.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:49 p.m.