Triple
T21569982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exposition Internationale du Surréalisme |
E532258
|
entity |
| Predicate | installationFeature |
P144289
|
FINISHED |
| Object | mannequins |
—
|
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: mannequins | Statement: [Exposition Internationale du Surréalisme, installationFeature, mannequins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installationFeature Context triple: [Exposition Internationale du Surréalisme, installationFeature, mannequins]
-
A.
installationMission
Indicates that an entity is assigned the task or mission of installing or setting up another entity.
-
B.
installationVariable
Indicates that a variable is associated with, defined for, or used during an installation process or configuration.
-
C.
installationForm
Indicates the specific method, configuration, or format in which something is installed or set up.
-
D.
installationCommand
Indicates the command or set of commands used to install a particular software, package, or component.
-
E.
installationContext
Indicates the situational or environmental setting in which an installation occurs or is intended to function.
- F. None of above. chosen
Provenance (4 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cb9718819094fc95b25df68bd1 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:30 p.m.