Triple
T8471678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Font Manager |
E200293
|
entity |
| Predicate | storesFontResourcesAs |
P30258
|
FINISHED |
| Object | FOND resources |
—
|
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: FOND resources | Statement: [Font Manager, storesFontResourcesAs, FOND resources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesFontResourcesAs Context triple: [Font Manager, storesFontResourcesAs, FOND resources]
-
A.
usesAlphabetResources
Indicates that an entity makes use of alphabet-related resources (such as letters, character sets, or alphabet-based tools) in performing an action or function.
-
B.
hasGlyphRepertoireSize
Indicates the number of distinct glyphs included in an entity’s glyph repertoire.
-
C.
traditionalResource
Indicates that one entity is a resource or practice that has been passed down through tradition and is recognized as part of a longstanding cultural or customary system used by another entity.
-
D.
storesObjectsAs
chosen
Indicates that one entity keeps or maintains other entities within it as stored items or contents.
-
E.
resourceExtracted
Indicates that a resource has been obtained or taken from a source entity, typically through an extraction process.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f3a81881908f20514579945ffa |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.