Triple
T2749128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Women Ironing |
E60940
|
entity |
| Predicate | relatedThemeInArtistOeuvre |
P29303
|
FINISHED |
| Object | ballet dancers |
—
|
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: ballet dancers | Statement: [Women Ironing, relatedThemeInArtistOeuvre, ballet dancers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedThemeInArtistOeuvre Context triple: [Women Ironing, relatedThemeInArtistOeuvre, ballet dancers]
-
A.
relatedWorkByArtist
Indicates that one work is connected to another through having been created by the same artist.
-
B.
associatedWithArtForm
chosen
Indicates a relationship where an entity is connected or linked to a particular art form, such as by practice, creation, representation, or influence.
-
C.
subjectRelationToArtist
Indicates the nature of the relationship or connection that the subject has to the artist.
-
D.
chronologyWithinArtistOeuvre
Indicates the temporal ordering of works within a single artist’s body of work, specifying how one piece relates in time to others by the same artist.
-
E.
artworkBy
Indicates that one entity is the creator or artist responsible for producing the other entity as an artwork.
- 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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb517a00819084fd8f8933a25212 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd829f1e88190aab1d54f87c69714 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.