Triple
T22678234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libre Baskerville |
E560404
|
entity |
| Predicate | kerning |
P149208
|
FINISHED |
| Object | optimized for text sizes |
—
|
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: optimized for text sizes | Statement: [Libre Baskerville, kerning, optimized for text sizes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kerning Context triple: [Libre Baskerville, kerning, optimized for text sizes]
-
A.
inkType
Indicates the specific kind or category of ink associated with or used by an entity.
-
B.
typographer
Indicates that an entity is a person or agent whose role is to design, arrange, or set type for printed or digital text.
-
C.
hasLigatures
Indicates that one writing system, font, or text includes combined character forms (ligatures) that join two or more individual glyphs into a single symbol.
-
D.
fillType
Indicates the manner or pattern in which an area, shape, or container is filled (e.g., solid, gradient, pattern, or other fill style).
-
E.
lining
Indicates that one entity forms a layer or covering along the inner or outer surface 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1785e4e7481909f1ebd6d8dbd6585 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:11 p.m.