Triple
T29547184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bauhaus preliminary course |
E749659
|
entity |
| Predicate | notableStudentWorkType |
P26054
|
FINISHED |
| Object | abstract reliefs |
—
|
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: abstract reliefs | Statement: [Bauhaus preliminary course, notableStudentWorkType, abstract reliefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStudentWorkType Context triple: [Bauhaus preliminary course, notableStudentWorkType, abstract reliefs]
-
A.
notableStudentWork
Indicates that the subject has a student whose work is particularly notable or significant in relation to the subject.
-
B.
notableTypeOfWork
chosen
Indicates that a work is a significant or defining example within a particular type or category of work associated with an entity.
-
C.
notableWorkPresented
Indicates that a particular notable work was presented, exhibited, or showcased by an entity (such as a person or organization).
-
D.
notableProjectType
Indicates the type or category of a project for which an entity is particularly well-known or notable.
-
E.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 5:08 p.m.