Triple
T15205459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madame Cézanne with a Fan |
E363376
|
entity |
| Predicate | depictsHumanRole |
P17608
|
FINISHED |
| Object | artist’s wife |
—
|
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 wife | Statement: [Madame Cézanne with a Fan, depictsHumanRole, artist’s wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsHumanRole Context triple: [Madame Cézanne with a Fan, depictsHumanRole, artist’s wife]
-
A.
depictsPersonRole
chosen
Indicates that an image or representation shows a person in a specific role, function, or capacity.
-
B.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
C.
designedRole
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to another entity.
-
D.
roleOfPeopleOnIt
Indicates the specific roles or functions that people have in relation to a particular object, event, or context.
-
E.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b7964c8190bc8dc3444b94f15e |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97ee9d881908711dbe12a55283c |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:11 a.m.