Triple
T13870081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girolamo Riario |
E333425
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renaissance politician |
C22812
|
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: Renaissance politician Context triple: [Girolamo Riario, instanceOf, Renaissance politician]
-
A.
16th-century politician
A 16th-century politician is a historical public figure who engaged in governance, policy-making, and power negotiations within the complex religious, dynastic, and imperial conflicts of the 1500s.
-
B.
Renaissance philosopher
A Renaissance philosopher is a thinker from the 14th to 17th centuries who blended classical learning with emerging humanist, scientific, and religious ideas to explore questions about knowledge, ethics, politics, and the nature of humanity.
-
C.
Renaissance figure
A Renaissance figure is a historically significant individual from roughly the 14th to 17th centuries who contributed to the revival of classical learning and the flourishing of arts, sciences, and humanist thought in Europe.
-
D.
15th-century English politician
A 15th-century English politician is a historical figure who participated in the governance and political affairs of England during the 1400s, often through roles in Parliament, royal councils, or local administration.
-
E.
Renaissance-era figure
chosen
A Renaissance-era figure is an individual from roughly the 14th to 17th centuries who contributed to the period’s revival of classical learning, artistic innovation, scientific inquiry, or humanist thought.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:14 p.m.