Triple
T23796301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louvre-Lens |
E588549
|
entity |
| Predicate | architectOfExhibitionDesign |
P63690
|
FINISHED |
| Object | Studio Adrien Gardère |
—
|
NE NERFINISHED |
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: Studio Adrien Gardère | Statement: [Louvre-Lens, architectOfExhibitionDesign, Studio Adrien Gardère]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectOfExhibitionDesign Context triple: [Louvre-Lens, architectOfExhibitionDesign, Studio Adrien Gardère]
-
A.
exhibitionDesigner
chosen
Indicates that an entity is responsible for planning, organizing, and designing the layout and presentation of an exhibition for another entity or event.
-
B.
exhibitionUse
Indicates that something is used, intended, or designated for display in an exhibition or exhibit context.
-
C.
exhibitDesignGoal
Indicates that something embodies or demonstrates a particular design objective or intended design outcome.
-
D.
exhibitionRole
Indicates the specific function or capacity an entity has within the context of an exhibition (e.g., organizer, curator, exhibitor, or participant).
-
E.
fieldOfExhibition
Indicates the domain or area in which something is publicly presented, displayed, or exhibited.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6dc94d481908800385a58d2c452 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:48 p.m.