Triple
T16091346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bauhaus typography |
E390362
|
entity |
| Predicate | relatedTypeface |
P42388
|
FINISHED |
| Object | Universal typeface |
—
|
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: Universal typeface | Statement: [Bauhaus typography, relatedTypeface, Universal typeface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedTypeface Context triple: [Bauhaus typography, relatedTypeface, Universal typeface]
-
A.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
B.
faceType
Indicates the specific shape or structural category of a face that an entity possesses or is characterized by.
-
C.
hasTypography
chosen
Indicates that one entity uses, is associated with, or is characterized by a particular typographic style, font, or text layout.
-
D.
digitalFontsAvailable
Indicates that digital versions of fonts are available for use or distribution.
-
E.
typographicRole
Indicates the specific typographic function or role that an element plays within written or printed content.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.