Triple
T18952222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | relational aesthetics |
E463681
|
entity |
| Predicate | viewsArtworkAs |
P61226
|
FINISHED |
| Object | social situation |
—
|
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: social situation | Statement: [relational aesthetics, viewsArtworkAs, social situation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsArtworkAs Context triple: [relational aesthetics, viewsArtworkAs, social situation]
-
A.
viewsArtAs
chosen
Indicates that one entity regards or interprets another entity as a form or example of art.
-
B.
artwork
Indicates that one entity is an artwork created, presented, or associated with another entity (such as an artist, collection, or institution).
-
C.
artworkBy
Indicates that one entity is the creator or artist responsible for producing the other entity as an artwork.
-
D.
appearsInWorkOfArt
Indicates that an entity is depicted, represented, or otherwise featured within a particular work of art.
-
E.
viewsWorksAs
Indicates that one entity regards or interprets another entity as functioning in a particular role, capacity, or way of working.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d54385e08190903a054681352d11 |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon