Triple
T30936714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukul Dey |
E788140
|
entity |
| Predicate | associatedArtTechnique |
P14965
|
FINISHED |
| Object | use of fine lines in drypoint |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: use of fine lines in drypoint | Statement: [Mukul Dey, associatedArtTechnique, use of fine lines in drypoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedArtTechnique Context triple: [Mukul Dey, associatedArtTechnique, use of fine lines in drypoint]
-
A.
artisticTechnique
chosen
Indicates the method, style, or process used to create or execute an artistic work.
-
B.
artSpecialty
Indicates that an entity’s primary focus, expertise, or specialization is in a particular art form or artistic domain.
-
C.
artisticMedium
Indicates the material or technique used to create an artwork or artistic expression.
-
D.
associatedWithArtForm
Indicates a relationship where an entity is connected or linked to a particular art form, such as by practice, creation, representation, or influence.
-
E.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
- F. None of above.
Provenance (3 batches)
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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:52 p.m.