Triple
T23437243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Lotharingia |
E563497
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval monarchic office |
C27640
|
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 monarchic office Context triple: [King of Lotharingia, instanceOf, medieval monarchic office]
-
A.
medieval public office
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.
monarchical institution
A monarchical institution is a governing body or system centered around a hereditary or otherwise singular sovereign authority that embodies the continuity, legitimacy, and symbolic unity of a state or polity.
-
C.
medieval king
chosen
A medieval king is a sovereign ruler who holds supreme political, military, and often religious authority over a kingdom, typically justified by hereditary right and divine sanction.
-
D.
princely office
A princely office is an institutional role or position held by a prince or princely figure, encompassing the authority, duties, and ceremonial functions associated with governing or representing a principality or royal domain.
-
E.
dynastic office
A dynastic office is a formal position of authority or responsibility that is inherited within a family line, typically passing from one generation to the next.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 5:50 p.m.