Triple
T9811968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Éomer |
E238294
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Third Marshal of the Riddermark |
C26898
|
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: Third Marshal of the Riddermark Context triple: [Éomer, instanceOf, Third Marshal of the Riddermark]
-
A.
Count Palatine
A Count Palatine is a noble title historically granted to a count who exercised sovereign or semi-sovereign authority within their territory, often with special judicial and administrative powers delegated directly by a monarch or emperor.
-
B.
Duke of Courland
The Duke of Courland was the hereditary ruler of the Duchy of Courland and Semigallia, a semi-autonomous Baltic state under Polish-Lithuanian suzerainty from the 16th to 18th centuries.
-
C.
Duke of Lorraine
The Duke of Lorraine is a noble title historically held by the sovereign ruler of the Duchy of Lorraine, a strategically important region in northeastern France that played a key role in European dynastic and territorial politics.
-
D.
Duke of Swabia
The Duke of Swabia was a high-ranking medieval noble who ruled the historical region of Swabia within the Holy Roman Empire, holding significant military, political, and territorial authority.
-
E.
Duke of Saxony
The Duke of Saxony is a high-ranking noble title historically held by rulers of the Saxony region in present-day Germany, signifying territorial authority, military leadership, and political influence within the Holy Roman Empire and later German states.
- F. None of above. chosen
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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:30 p.m.