Triple
T33595100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilbert Prousch |
E860538
|
entity |
| Predicate | notableExhibitionFormat |
P47681
|
FINISHED |
| Object | large-scale photo-based panels |
—
|
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: large-scale photo-based panels | Statement: [Gilbert Prousch, notableExhibitionFormat, large-scale photo-based panels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableExhibitionFormat Context triple: [Gilbert Prousch, notableExhibitionFormat, large-scale photo-based panels]
-
A.
hasExhibitFormat
Indicates the specific format or medium in which an exhibit is presented or made available.
-
B.
exhibitionMedium
chosen
Indicates the material or format through which something is exhibited or displayed.
-
C.
exhibitionType
Indicates the specific category or kind of exhibition associated with an entity (e.g., art show, trade fair, scientific exhibit).
-
D.
exhibitionFeature
Indicates that an exhibition includes or highlights a particular item, work, or element as one of its featured components.
-
E.
exhibitedAs
Indicates that something is presented or displayed in a particular context, such as in a show, gallery, or exhibition.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:41 a.m.