Triple
T34848073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Roman Emperor’s representatives |
E1004526
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial envoy |
C34157
|
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: imperial envoy Context triple: [Holy Roman Emperor’s representatives, instanceOf, imperial envoy]
-
A.
imperial official
An imperial official is a government functionary appointed by a sovereign empire to administer its laws, collect revenues, and enforce imperial authority within a designated jurisdiction.
-
B.
imperial governor
An imperial governor is a high-ranking official appointed by a central empire to administer, oversee, and enforce its authority, laws, and policies within a specific province or territory.
-
C.
diplomatic official
chosen
A diplomatic official is a government-appointed representative who manages and promotes their nation's political, economic, and cultural interests in foreign states or international organizations.
-
D.
imperial court office
An imperial court office is an administrative position or bureau within an empire’s central government responsible for managing specific functions of state, such as finance, justice, ceremony, or military affairs, under the authority of the sovereign.
-
E.
Roman diplomat
A Roman diplomat is an official representative of the Roman state responsible for negotiating treaties, managing foreign relations, and maintaining alliances with other powers in accordance with Roman political and legal traditions.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.