Triple
T38170976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bauhaus |
E1000072
|
entity |
| Predicate | invitedDesignerRole |
P142196
|
FINISHED |
| Object | guest designer |
—
|
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: guest designer | Statement: [Bauhaus, invitedDesignerRole, guest designer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invitedDesignerRole Context triple: [Bauhaus, invitedDesignerRole, guest designer]
-
A.
invitedDesigner
Indicates that one entity has requested or called upon a designer to participate in an event, project, or activity.
-
B.
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.
-
C.
designedRole
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to another entity.
-
D.
officeHeldByDesigner
Indicates that a particular office or official position is occupied or held by a given designer.
-
E.
designerType
chosen
Indicates the specific kind or category of designer role associated with an 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.