Triple
T21815696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impala SS script and logo |
E538600
|
entity |
| Predicate | typographyStyle |
P42388
|
FINISHED |
| Object | script lettering |
—
|
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: script lettering | Statement: [Impala SS script and logo, typographyStyle, script lettering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typographyStyle Context triple: [Impala SS script and logo, typographyStyle, script lettering]
-
A.
styleFamily
Indicates that one style is grouped within the same stylistic family or category as another style.
-
B.
hasTypography
chosen
Indicates that one entity uses, is associated with, or is characterized by a particular typographic style, font, or text layout.
-
C.
characterStyle
Indicates how a character is visually or typographically presented, such as its font, weight, size, or decorative attributes.
-
D.
typographicRole
Indicates the specific typographic function or role that an element plays within written or printed content.
-
E.
typographicLegacy
Indicates a relationship where one typographic style, convention, or feature is inherited from, derived from, or historically influenced by another.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cc99bbc8190bf074930f361af7d |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:54 p.m.