Triple
T27737915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MatIcon |
E697572
|
entity |
| Predicate | defaultFontSet |
P131100
|
FINISHED |
| Object | material-icons |
—
|
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: material-icons | Statement: [MatIcon, defaultFontSet, material-icons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultFontSet Context triple: [MatIcon, defaultFontSet, material-icons]
-
A.
defaultFontOf
chosen
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).
-
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.
digitalFontsAvailable
Indicates that digital versions of fonts are available for use or distribution.
-
D.
characterSetType
Indicates the type or category of character set associated with or used by an entity.
-
E.
defaultTextForegroundColor
Indicates the relationship where a default color is assigned to be used for rendering the foreground (typically text) content of an element or interface.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 3:13 p.m.