Triple
T6964610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunswick-Lüneburg court at Celle |
E161456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early modern court |
C13331
|
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: early modern court Context triple: [Brunswick-Lüneburg court at Celle, instanceOf, early modern court]
-
A.
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.
-
B.
early modern political institution
chosen
An early modern political institution is an organized structure of authority and governance, such as monarchies, parliaments, courts, or bureaucracies, that emerged or operated roughly between the 15th and 18th centuries to regulate power, law, and social order.
-
C.
early modern polity
An early modern polity is a territorially bounded, politically organized community between roughly 1500 and 1800 that exercised authority through evolving institutions of governance, law, and sovereignty amid processes of state formation and imperial expansion.
-
D.
early modern state
An early modern state is a centralized political entity that emerged in Europe between the 15th and 18th centuries, characterized by growing bureaucratic administration, territorial sovereignty, standing armies, and increasingly standardized systems of law and taxation.
-
E.
royal courtier
A royal courtier is a member of a monarch’s household who attends the ruler, manages or influences court affairs, and advances political, social, or personal interests within the royal court.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:30 p.m.