Triple
T25426429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altsys |
E637126
|
entity |
| Predicate | FontographerType |
P158496
|
FINISHED |
| Object | font editor |
—
|
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: font editor | Statement: [Altsys, FontographerType, font editor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FontographerType Context triple: [Altsys, FontographerType, font editor]
-
A.
FontographerFirstReleased
Indicates the date or time when Fontographer was first released.
-
B.
hasTypography
Indicates that one entity uses, is associated with, or is characterized by a particular typographic style, font, or text layout.
-
C.
figureType
Indicates that one entity is classified as a specific type or category of figure in relation to another entity.
-
D.
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.
-
E.
typographicLegacy
Indicates a relationship where one typographic style, convention, or feature is inherited from, derived from, or historically influenced by another.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bfdb748190abfd40ed1838d9aa |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:57 p.m.