Triple
T3232816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usher of the Order of the Garter |
E67781
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | office of the Order of the Garter |
C4081
|
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: office of the Order of the Garter Context triple: [Usher of the Order of the Garter, instanceOf, office of the Order of the Garter]
-
A.
clerk of the Privy Seal
A clerk of the Privy Seal was an official responsible for preparing, drafting, and processing documents that required authentication by the monarch’s privy seal, often serving as an intermediary between petitioners and higher offices of royal administration.
-
B.
heraldic office
chosen
A heraldic office is an official institution or position responsible for designing, granting, recording, and regulating coats of arms and other heraldic symbols.
-
C.
episcopal palace
An episcopal palace is the official residence and administrative center of a bishop or archbishop, typically associated with a cathedral and used for ecclesiastical governance and ceremonial functions.
-
D.
order of knighthood
An order of knighthood is an organized society or institution, often established by a monarch or state, that confers ranks of honor and chivalric titles on individuals for distinguished service or merit.
-
E.
royal court
A royal court is the formal assembly of a monarch’s household, advisors, officials, and attendants who support, counsel, and ceremonially represent the sovereign’s authority and governance.
- 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:08 p.m.