Triple
T4972229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V&A Dundee |
E111678
|
entity |
| Predicate | notableExhibitionType |
P3934
|
FINISHED |
| Object | temporary design exhibitions |
—
|
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: temporary design exhibitions | Statement: [V&A Dundee, notableExhibitionType, temporary design exhibitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableExhibitionType Context triple: [V&A Dundee, notableExhibitionType, temporary design exhibitions]
-
A.
exhibitionType
chosen
Indicates the specific category or kind of exhibition associated with an entity (e.g., art show, trade fair, scientific exhibit).
-
B.
exhibition
Indicates that an entity is organizing, hosting, or serving as a public display or presentation of another entity (such as artworks, objects, or information).
-
C.
hasExhibitionsAbout
Indicates that one entity organizes or presents exhibitions whose subject matter concerns another entity.
-
D.
exhibitionSource
Indicates the origin or provider from which an exhibition or displayed work is sourced or obtained.
-
E.
exhibitionMedium
Indicates the material or format through which something is exhibited or displayed.
- 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.