Triple
T22996547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pictures of Dust |
E572209
|
entity |
| Predicate | artisticProcessStep |
P14965
|
FINISHED |
| Object | collecting dust from museum floors |
—
|
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: collecting dust from museum floors | Statement: [Pictures of Dust, artisticProcessStep, collecting dust from museum floors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artisticProcessStep Context triple: [Pictures of Dust, artisticProcessStep, collecting dust from museum floors]
-
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.
artisticDirection
Indicates that one entity is responsible for guiding and overseeing the creative or aesthetic vision of another entity or project.
-
D.
artUse
Indicates that one entity uses, applies, or employs another entity within an artistic or creative context.
-
E.
artwork
Indicates that one entity is an artwork created, presented, or associated with another entity (such as an artist, collection, or institution).
- 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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f3186c81909e0d5177029a72ae |
completed | April 29, 2026, 4:02 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.