Triple
T13110663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vogt (advocate) |
E310961
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval office |
C24745
|
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: medieval office Context triple: [Vogt (advocate), instanceOf, medieval office]
-
A.
medieval public office
chosen
A medieval public office is an institutional role within the governance structures of the Middle Ages, endowed with specific legal authority, duties, and privileges to administer justice, manage resources, or represent sovereign power on behalf of a ruler or community.
-
B.
medieval court
A medieval court is the political and social center surrounding a monarch or noble, where governance, justice, ceremony, and daily life of the ruling elite are conducted.
-
C.
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.
-
D.
medieval institution
A medieval institution is an organized social, political, religious, or economic structure—such as the Church, feudal lordship, or guilds—that governed relationships, authority, and daily life in medieval society.
-
E.
medieval politician
A medieval politician is a power-seeking figure who navigates feudal hierarchies, religious authority, and shifting alliances to influence governance and control resources in a pre-modern society.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:05 p.m.