Triple
T4483057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolfgang Tillmans |
E100175
|
entity |
| Predicate | hasWorkTheme |
P18026
|
FINISHED |
| Object | LGBTQ+ identity |
—
|
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: LGBTQ+ identity | Statement: [Wolfgang Tillmans, hasWorkTheme, LGBTQ+ identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkTheme Context triple: [Wolfgang Tillmans, hasWorkTheme, LGBTQ+ identity]
-
A.
hasPersonalThemes
Indicates that something (such as a work, message, or expression) involves themes that are personal, intimate, or directly related to an individual’s own experiences or inner life.
-
B.
associatedWithWorkTheme
Indicates a relationship where something is connected or related to a particular work theme or subject matter.
-
C.
hasWorkSubject
chosen
Indicates that a work (such as a document, artwork, or project) is about or concerns a particular subject or topic.
-
D.
hasWorkStyle
Indicates the type or manner in which an entity typically performs work or carries out tasks.
-
E.
supportsThemeOf
Indicates that one entity reinforces, aligns with, or contributes to the central theme expressed by 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:36 p.m.