Triple
T31387453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorenzo the Magnificent’s circle |
E800635
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | patronage network |
C28040
|
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: patronage network Context triple: [Lorenzo the Magnificent’s circle, instanceOf, patronage network]
-
A.
parliamentary network
A parliamentary network is a structured system of relationships and interactions among legislators, parties, committees, and external stakeholders that facilitates the flow of information, influence, and decision-making within and around a parliament.
-
B.
policy network
A policy network is a neural network that maps states or observations directly to actions or action probabilities in reinforcement learning, defining the agent’s behavior strategy.
-
C.
royal patronage
chosen
Royal patronage is the support, protection, and sponsorship provided by a monarch or royal household to individuals, institutions, or projects, often in the arts, religion, or politics, to enhance both the recipients’ status and the crown’s influence.
-
D.
judicial network
A judicial network is a structured system of interconnected courts, judges, and legal institutions that interact through case decisions, precedents, and administrative relationships to shape and apply the law.
-
E.
state-controlled network of organizations
A state-controlled network of organizations is a coordinated system of entities whose structures, activities, and decision-making are centrally directed or heavily influenced by government authorities to achieve political, economic, or social objectives.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
Created at: April 29, 2026, 9:19 p.m.