Triple
T22678232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libre Baskerville |
E560404
|
entity |
| Predicate | hinting |
P149207
|
FINISHED |
| Object | optimized for screen |
—
|
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 screen | Statement: [Libre Baskerville, hinting, optimized for screen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hinting Context triple: [Libre Baskerville, hinting, optimized for screen]
-
A.
holding
Indicates that one entity is physically grasping, carrying, or keeping another entity in its possession or control.
-
B.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
C.
hold
Indicates that one entity physically grasps, carries, or keeps another entity in its possession or control.
-
D.
helpsIn
Indicates that one entity provides assistance, support, or aid to another entity in performing or achieving a particular task, activity, or goal.
-
E.
indicatedFor
Indicates...that one entity (typically a treatment, procedure, or product) is recommended or appropriate for use in relation to another entity (such as a condition, symptom, or patient group).
- 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.