Triple
T32550330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Museum of European Garden Art |
E831955
|
entity |
| Predicate | typeOfArtPresented |
P91702
|
FINISHED |
| Object | garden art |
—
|
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: garden art | Statement: [Museum of European Garden Art, typeOfArtPresented, garden art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfArtPresented Context triple: [Museum of European Garden Art, typeOfArtPresented, garden art]
-
A.
artworkType
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.
artSpecialty
chosen
Indicates that an entity’s primary focus, expertise, or specialization is in a particular art form or artistic domain.
-
D.
exhibitionType
Indicates the specific category or kind of exhibition associated with an entity (e.g., art show, trade fair, scientific exhibit).
-
E.
artCategory
Indicates the classification relationship where an artwork is assigned to a particular artistic category or genre.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a006be462288190ae18e1567e2ad29f |
completed | May 10, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_6a0069e7a424819098d38458c3823605 |
completed | May 10, 2026, 11:20 a.m. |
Created at: May 1, 2026, 1:02 a.m.