Triple
T22859819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambroise |
E566884
|
entity |
| Predicate | typographicContrast |
P43203
|
FINISHED |
| Object | extreme |
—
|
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: extreme | Statement: [Ambroise, typographicContrast, extreme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typographicContrast Context triple: [Ambroise, typographicContrast, extreme]
-
A.
contrastRatio
chosen
Indicates the proportional difference in luminance or intensity between two visual elements being compared.
-
B.
hasTypography
Indicates that one entity uses, is associated with, or is characterized by a particular typographic style, font, or text layout.
-
C.
typographicRole
Indicates the specific typographic function or role that an element plays within written or printed content.
-
D.
typographicLegacy
Indicates a relationship where one typographic style, convention, or feature is inherited from, derived from, or historically influenced by another.
-
E.
typographer
Indicates that an entity is a person or agent whose role is to design, arrange, or set type for printed or digital text.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ec082c08190943e6cfc2e25c5cc |
completed | April 29, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:37 p.m.