Triple
T6884647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Rosenthal |
E158885
|
entity |
| Predicate | hasPhotographicGenre |
P62927
|
FINISHED |
| Object | war photography |
—
|
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: war photography | Statement: [Joe Rosenthal, hasPhotographicGenre, war photography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhotographicGenre Context triple: [Joe Rosenthal, hasPhotographicGenre, war photography]
-
A.
isPhotographicSubject
Indicates that an entity serves as the subject or main focus captured in a photograph taken by another entity.
-
B.
photographyGenre
chosen
Indicates the specific genre or style of photography that characterizes a photographic work or activity.
-
C.
hasPhotographicConvention
Indicates that there is an established photographic style, rule, or convention governing how the related entities are visually represented in photographs.
-
D.
hasPhotographicProcess
Indicates that something is associated with, created by, or characterized through a specific photographic process or technique.
-
E.
hasPhotograph
Indicates that one entity possesses, includes, or is associated with a photograph depicting or representing another entity.
- 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_69c688342f6c8190ad7eea6ba262db99 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d90a2590819092ff253dd66ebe8b |
completed | March 27, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:23 p.m.