Triple
T31639917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hortar |
E807419
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Alemannic chieftain |
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 chieftain Context triple: [Hortar, instanceOf, Alemannic chieftain]
-
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.
Cherusci nobleman
A Cherusci nobleman is a high-ranking member of the ancient Germanic Cherusci tribe’s aristocracy, wielding political, military, and social influence within the tribal hierarchy.
-
C.
Hungarian chieftain
A Hungarian chieftain is a tribal leader of the early Magyars who held military, political, and social authority over a clan or tribal confederation in the Carpathian Basin during the 9th–10th centuries.
-
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.
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.
- 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.