Triple
T5902982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord High Steward of Sweden |
E131272
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | great officer of the realm of Sweden |
C4558
|
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: great officer of the realm of Sweden Context triple: [Lord High Steward of Sweden, instanceOf, great officer of the realm of Sweden]
-
A.
Swedish royal
A Swedish royal is a member of Sweden’s monarchy, belonging to the royal family by birth or marriage and often performing ceremonial, diplomatic, and representative duties for the nation.
-
B.
Swedish count
A Swedish count is a noble title in Sweden, historically ranking below a duke and above a baron, often associated with hereditary privileges, land ownership, and social status within the Swedish aristocracy.
-
C.
officer of state
chosen
An officer of state is a high-ranking public official who holds a formal position within a government or monarchy, responsible for executing specific constitutional, administrative, or ceremonial duties of the state.
-
D.
Swedish noble
A Swedish noble is a member of Sweden’s historically privileged aristocratic estate, traditionally holding hereditary titles, social status, and often land or political influence within the Swedish realm.
-
E.
peer of the Kingdom of England
A peer of the Kingdom of England is a noble holding one of the hereditary or life dignities (duke, marquess, earl, viscount, or baron) that conferred membership in the English peerage and historically a seat in the House of Lords.
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:58 p.m.