Triple
T27130565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Void (Le Vide) |
E681551
|
entity |
| Predicate | exhibitionSpaceTreatment |
P163089
|
FINISHED |
| Object | display fixtures removed |
—
|
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: display fixtures removed | Statement: [The Void (Le Vide), exhibitionSpaceTreatment, display fixtures removed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhibitionSpaceTreatment Context triple: [The Void (Le Vide), exhibitionSpaceTreatment, display fixtures removed]
-
A.
exhibitionSpaceTreatment
chosen
Indicates how an exhibition space is arranged, designed, or modified to present or support what is being exhibited.
-
B.
exhibitionSpaceType
Indicates the specific kind or category of space used to display or present exhibitions.
-
C.
exhibitionUse
Indicates that something is used, intended, or designated for display in an exhibition or exhibit context.
-
D.
gallerySpace
Indicates that one entity serves as a gallery or exhibition space for displaying the other entity.
-
E.
exhibitionDesigner
Indicates that an entity is responsible for planning, organizing, and designing the layout and presentation of an exhibition for another entity or event.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:04 a.m.