Triple
T1646253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow House, Arles |
E35587
|
entity |
| Predicate | themeInArtHistory |
P15999
|
FINISHED |
| Object | artist communities |
—
|
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 communities | Statement: [Yellow House, Arles, themeInArtHistory, artist communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeInArtHistory Context triple: [Yellow House, Arles, themeInArtHistory, artist communities]
-
A.
artisticTheme
chosen
Indicates the central artistic subject, concept, or motif that characterizes or is expressed by a creative work.
-
B.
artHistoricalInterpretation
Indicates an interpretive relationship where an artwork is analyzed or explained through art-historical methods, theories, or contextual understanding.
-
C.
inArtSince
Indicates that an entity has been involved or active in the field of art starting from a specified time.
-
D.
artMovement
Indicates the artistic movement or style with which an artwork, artist, or cultural work is associated.
-
E.
heritageTheme
Indicates that something is associated with, represents, or is categorized under a particular cultural or historical heritage theme.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a919306fd48190a245fc95e0e759d9 |
completed | March 5, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69a907cc9d348190b76b0d3f596e5a81 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.