Triple
T22626272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Untitled (to Don Judd, colorist) |
E558425
|
entity |
| Predicate | usesReadymadeObjects |
P148971
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Untitled (to Don Judd, colorist), usesReadymadeObjects, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesReadymadeObjects Context triple: [Untitled (to Don Judd, colorist), usesReadymadeObjects, true]
-
A.
usesSupportMaterial
Indicates that an entity relies on or incorporates additional supporting materials or resources to carry out an action or fulfill a function.
-
B.
usesMake
Indicates that one entity employs, applies, or utilizes another entity as a means, tool, or method to achieve some purpose.
-
C.
madeWith
Indicates that one entity is created, produced, or constructed using another entity as a material, ingredient, or component.
-
D.
usesElementsOf
Indicates that one entity incorporates, applies, or draws upon components, principles, or features derived from another entity.
-
E.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
- F. None of above. chosen
Provenance (4 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3d55b081908930ebff4372154f |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:01 p.m.