Triple
T29011110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple ImageWriter printers |
E736566
|
entity |
| Predicate | supportsFont |
P203
|
FINISHED |
| Object | bitmap 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: bitmap fonts | Statement: [Apple ImageWriter printers, supportsFont, bitmap fonts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFont Context triple: [Apple ImageWriter printers, supportsFont, bitmap fonts]
-
A.
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.
-
B.
supportsParentFont
Indicates that an entity provides or maintains compatibility with the font used by its parent entity.
-
C.
supportsFontSmoothing
Indicates that one entity provides or enables font smoothing capabilities for another entity or context.
-
D.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
E.
usesOpenTypeFeatures
Indicates that one entity employs or supports OpenType typographic features in relation to another entity or context.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a02efcb13248190a0bef09ba7869ada |
completed | May 12, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_6a024995e1d081908783ca294d1397c3 |
completed | May 11, 2026, 9:26 p.m. |
Created at: April 28, 2026, 9:42 a.m.