Triple
T7368524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jusepe de Ribera |
E169931
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tenebrist artist |
C817
|
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: Tenebrist artist Context triple: [Jusepe de Ribera, instanceOf, Tenebrist artist]
-
A.
Baroque artist
chosen
A Baroque artist is a creator from the 17th–early 18th century who employs dramatic contrast, rich detail, and dynamic movement to evoke intense emotion and grandeur in their works.
-
B.
Mannerist painter
A Mannerist painter is an artist of the 16th century who deliberately distorts proportion, space, and perspective to create stylized, elongated figures and complex, often tension-filled compositions that depart from High Renaissance balance and naturalism.
-
C.
Renaissance painter
A Renaissance painter is an artist from the 14th to 17th centuries who combined revived classical ideals with emerging techniques like linear perspective, naturalistic anatomy, and chiaroscuro to create human-centered, harmoniously composed works.
-
D.
late Renaissance artist
A late Renaissance artist is a creator working in the transitional period between the High Renaissance and early Baroque, blending classical balance and harmony with emerging interest in drama, emotion, and complex composition.
-
E.
High Renaissance artist
A High Renaissance artist is a masterful creator from the late 15th to early 16th century who harmoniously blends idealized naturalism, balanced composition, and humanist themes to achieve a pinnacle of artistic refinement.
- 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_69c68a5ade988190885b7175f63b7534 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:07 p.m.