Triple
T8649480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triadic Ballet |
E205061
|
entity |
| Predicate | designPrinciples |
P9626
|
FINISHED |
| Object | Bauhaus design principles |
—
|
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: Bauhaus design principles | Statement: [Triadic Ballet, designPrinciples, Bauhaus design principles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designPrinciples Context triple: [Triadic Ballet, designPrinciples, Bauhaus design principles]
-
A.
designPhilosophy
Indicates the guiding principles, values, or conceptual approach that shape how something is designed or created.
-
B.
principle1
Indicates that one entity serves as a primary rule, guideline, or foundational principle governing or guiding another entity.
-
C.
principle6
Indicates that one entity upholds, follows, or is governed by a specific sixth principle in a defined set of principles.
-
D.
typeOfPrinciples
chosen
Indicates a relationship where one entity specifies the kind or category of principles that another entity embodies, uses, or is governed by.
-
E.
designMethod
Indicates that one entity is used as the method, approach, or technique by which another entity is designed or created.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4813d0548190b203e594acc38c8f |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.