Triple
T31272805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portrait of the Artist’s Wife |
E797433
|
entity |
| Predicate | hasMainSubjectRole |
P192208
|
FINISHED |
| Object | artist’s spouse |
—
|
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 spouse | Statement: [Portrait of the Artist’s Wife, hasMainSubjectRole, artist’s spouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainSubjectRole Context triple: [Portrait of the Artist’s Wife, hasMainSubjectRole, artist’s spouse]
-
A.
hasSubjectRoleIn
chosen
Indicates that an entity serves in a specific subject role within a particular context, situation, or relationship.
-
B.
hasMainSubjectKey
Indicates that an entity is associated with a primary or principal subject identifier used as its main reference or key.
-
C.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
D.
hasPrimarySubject
Indicates that an entity is the main or principal subject associated with another entity or resource.
-
E.
hasHumanSubject
Indicates that an entity serves as the human participant or subject involved in an action, event, or relation.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: April 29, 2026, 9:13 p.m.