Triple
T29547052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bauhaus stage workshop |
E749657
|
entity |
| Predicate | headOfWorkshop |
P167013
|
FINISHED |
| Object | Lothar Schreyer |
—
|
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: Lothar Schreyer | Statement: [Bauhaus stage workshop, headOfWorkshop, Lothar Schreyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headOfWorkshop Context triple: [Bauhaus stage workshop, headOfWorkshop, Lothar Schreyer]
-
A.
headDescription
Indicates that one entity serves as a textual or semantic description of the head (primary) entity in the relationship.
-
B.
workshopInTitleIndicates
Indicates that the presence of the word "workshop" in a title signifies that the associated event, session, or item is a workshop.
-
C.
workshopMark
Indicates that an entity has been designated, labeled, or flagged in the context of a workshop-related process or activity.
-
D.
notableWorkshop
Indicates that an entity is a workshop distinguished by particular significance, prominence, or recognition (e.g., in impact, reputation, or importance).
-
E.
header
Indicates that one entity serves as a heading or title section that precedes and organizes the content of another entity.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cf3695c81908817bc14126fea9e |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6642e676c8190af0e6b1416eed6d2 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 5:08 p.m.