Triple
T29477054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Éomund |
E747677
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Marshal of the Mark |
C55783
|
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: Marshal of the Mark Context triple: [Éomund, instanceOf, Marshal of the Mark]
-
A.
Marshal of the Empire
A Marshal of the Empire is the highest-ranking military commander entrusted with supreme authority over imperial armies, strategy, and defense of the realm in the name of the sovereign.
-
B.
Third Marshal of the Riddermark
The Third Marshal of the Riddermark is a high-ranking Rohirrim military commander responsible for leading one of Rohan’s primary field armies and defending a designated region of the Riddermark.
-
C.
Lord Warden of the Marches
The Lord Warden of the Marches was a high-ranking royal official responsible for governing, defending, and administering justice in the turbulent border regions between England and Scotland (or Wales) during the late medieval and early modern periods.
-
D.
Saxon field marshal
A Saxon field marshal is a highest-ranking military officer from Saxony responsible for commanding large armies, directing overall strategy, and overseeing major military operations.
-
E.
Lord Marshal of England
The Lord Marshal of England was a high-ranking royal officer responsible for overseeing the king’s stables, military organization, and aspects of court ceremony and justice, particularly relating to chivalry and knighthood.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 4:01 p.m.