Triple
T35077552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagler faction |
E1012345
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Norwegian political faction |
C17983
|
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 Norwegian political faction Context triple: [Bagler faction, instanceOf, medieval Norwegian political faction]
-
A.
medieval political faction
chosen
A medieval political faction is an organized group of nobles, clergy, or urban elites who align around shared interests, loyalties, or claims to power, competing and negotiating within the feudal and dynastic structures of the Middle Ages.
-
B.
Norwegian noble
A Norwegian noble is a member of the historical aristocratic class in Norway, traditionally holding hereditary titles, land, and social privileges within the Norwegian realm.
-
C.
orcish faction
A brutal and warlike orcish faction united by strength, tribal honor, and conquest, often clashing with neighboring realms for territory and dominance.
-
D.
medieval Norwegian administrative district
A medieval Norwegian administrative district was a territorial unit used by the crown and local authorities to organize governance, taxation, justice, and military obligations within a defined region.
-
E.
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.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.