Triple
T29547526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Font Book |
E749668
|
entity |
| Predicate | managesFontsInDirectory |
P10599
|
FINISHED |
| Object | /Library/Fonts |
—
|
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: /Library/Fonts | Statement: [Font Book, managesFontsInDirectory, /Library/Fonts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesFontsInDirectory Context triple: [Font Book, managesFontsInDirectory, /Library/Fonts]
-
A.
digitalFontsAvailable
Indicates that digital versions of fonts are available for use or distribution.
-
B.
typicalFontSupport
Indicates that one entity (such as a system, application, or platform) normally includes or provides support for a particular font or set of fonts under standard conditions.
-
C.
fileManager
chosen
Indicates a relationship where an entity manages, organizes, or controls access to files or file-related operations for another entity.
-
D.
FontographerType
Indicates a relationship where an entity is classified as a type or category within the Fontographer system or schema.
-
E.
defaultFontOf
Indicates that one entity is the standard or fallback font used for rendering text in another entity (such as a document, style, or interface element).
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 28, 2026, 5:09 p.m.