Triple
T30523437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maison Jansen |
E776761
|
entity |
| Predicate | hasHeadDesignerRole |
P130376
|
FINISHED |
| Object | artistic director |
—
|
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: artistic director | Statement: [Maison Jansen, hasHeadDesignerRole, artistic director]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadDesignerRole Context triple: [Maison Jansen, hasHeadDesignerRole, artistic director]
-
A.
hasDesignAuthority
Indicates that one entity holds the recognized power or responsibility to make or approve design decisions affecting another entity.
-
B.
hasCreativeDirectorRoleAt
chosen
Indicates that an entity holds the position or responsibilities of a creative director at a specified organization or project.
-
C.
hasArchitectRole
Indicates that an entity holds or fulfills the role or function of an architect in relation to another entity or project.
-
D.
associatedWithDesignerRole
Indicates that an entity has a relationship or involvement with a designer role, such as performing, supporting, or being linked to design-related responsibilities.
-
E.
designedHead
Indicates that one entity is the primary designer or creator responsible for the conception or design of another entity.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 29, 2026, 8:17 p.m.