Triple
T29132505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Sélavy |
E738416
|
entity |
| Predicate | notablePhotographicSeriesBy |
P38499
|
FINISHED |
| Object | Man Ray |
E187466
|
NE 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: Man Ray | Statement: [Rose Sélavy, notablePhotographicSeriesBy, Man Ray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePhotographicSeriesBy Context triple: [Rose Sélavy, notablePhotographicSeriesBy, Man Ray]
-
A.
notablePhotographer
Indicates that the subject is a photographer who is recognized as notable or significant in some context.
-
B.
photographerOfNotableImage
Indicates that a person is the photographer who captured a specific notable or widely recognized image.
-
C.
hasPhotographicSeries
chosen
Indicates that one entity is associated with, or is the subject of, a specific photographic series created or maintained by another entity.
-
D.
hasPhotographicSignificance
Indicates that something holds notable importance or relevance in the context of photography, such as for documentation, artistic value, or visual record.
-
E.
imageMadeFamousBy
Indicates that an image became widely known or notable as a result of association with, or promotion by, a particular entity.
- F. None of above.
Provenance (4 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a0302d9d2d88190b20429530775b035 |
completed | May 12, 2026, 10:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2550588e308190b0375f1b9a4f7f82 |
completed | June 7, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_6a0302289128819085428f3d544c2fb9 |
completed | May 12, 2026, 10:34 a.m. |
Created at: April 28, 2026, 11:32 a.m.