Triple
T31327180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claes Oldenburg: Mouse Museum/Ray Gun Wing |
E798917
|
entity |
| Predicate | workTypeDiscussed |
P86785
|
FINISHED |
| Object | sculptural installation |
—
|
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: sculptural installation | Statement: [Claes Oldenburg: Mouse Museum/Ray Gun Wing, workTypeDiscussed, sculptural installation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workTypeDiscussed Context triple: [Claes Oldenburg: Mouse Museum/Ray Gun Wing, workTypeDiscussed, sculptural installation]
-
A.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
B.
associatedWorkType
chosen
Indicates the type or category of work with which an entity is associated (e.g., publication, artwork, performance).
-
C.
workTypeContributedTo
Indicates that an entity contributed to the creation, development, or production of a particular type of work.
-
D.
workTypeOfSetting
Indicates the type or nature of work activity that characterizes or occurs within a particular setting.
-
E.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:15 p.m.