Triple
T2909989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whistler's Mother |
E63657
|
entity |
| Predicate | subjectRelationshipToArtist |
P33013
|
FINISHED |
| Object | artist's mother |
—
|
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: artist's mother | Statement: [Whistler's Mother, subjectRelationshipToArtist, artist's mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectRelationshipToArtist Context triple: [Whistler's Mother, subjectRelationshipToArtist, artist's mother]
-
A.
subjectRelationToArtist
chosen
Indicates the nature of the relationship or connection that the subject has to the artist.
-
B.
relatedWorkByArtist
Indicates that one work is connected to another through having been created by the same artist.
-
C.
influencedArtist
Indicates that one artist has had a significant impact on the style, work, or development of another artist.
-
D.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
E.
performerRelationshipContext
Indicates the contextual nature or circumstances of the relationship between a performer and another entity (such as an event, work, or role).
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0e899808190a348e1e71116d0a5 |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.