Triple
T8509128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fountain |
E201407
|
entity |
| Predicate | artisticMethod |
P14965
|
FINISHED |
| Object | appropriation of everyday object |
—
|
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: appropriation of everyday object | Statement: [Fountain, artisticMethod, appropriation of everyday object]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artisticMethod Context triple: [Fountain, artisticMethod, appropriation of everyday object]
-
A.
artisticFunction
Indicates that one entity serves a creative, expressive, or aesthetic role or purpose in relation to another entity.
-
B.
artisticTechnique
chosen
Indicates the method, style, or process used to create or execute an artistic work.
-
C.
artisticField
Indicates the artistic domain or creative discipline in which an entity is active or associated.
-
D.
artisticStyle
Indicates the artistic movement, style, or aesthetic approach that characterizes how something is created or visually expressed.
-
E.
artisticTraining
Indicates that one entity has provided, received, or been involved in formal or informal instruction or education in the arts from or with 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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5df74e8819086b1445cc907e371 |
completed | March 31, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:15 p.m.