Triple
T23437824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benesse House Park |
E563511
|
entity |
| Predicate | hasTypeOfArtwork |
P3050
|
FINISHED |
| Object | site-specific installations |
—
|
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: site-specific installations | Statement: [Benesse House Park, hasTypeOfArtwork, site-specific installations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfArtwork Context triple: [Benesse House Park, hasTypeOfArtwork, site-specific installations]
-
A.
artworkType
chosen
Indicates the specific category or kind of artwork that characterizes the relationship between the subject and the artwork.
-
B.
typeOfWorksListed
Indicates that the kinds or categories of works associated with an entity are specified or enumerated.
-
C.
hasArtCollection
Indicates that an entity possesses, maintains, or is associated with a collection of artworks.
-
D.
hasSculptureType
Indicates that an entity is associated with a sculpture and specifies the type or category of that sculpture.
-
E.
hasTypeOfWorkExhibited
Indicates that a subject (such as an exhibition or venue) features or displays a particular type or category of work.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5dda7448190b6c686e0db4f4f2f |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:50 p.m.