Triple
T27636588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MatSnackBar |
E696486
|
entity |
| Predicate | supportsTheming |
P83860
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [MatSnackBar, supportsTheming, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTheming Context triple: [MatSnackBar, supportsTheming, true]
-
A.
supportsThemingSystem
chosen
Indicates that an entity is compatible with and can operate using a theming system for customizable appearance or style.
-
B.
supportsThemingFormat
Indicates that an entity is compatible with and can correctly handle a particular theming format or style specification.
-
C.
supportsThemeOf
Indicates that one entity reinforces, aligns with, or contributes to the central theme expressed by another entity.
-
D.
isThemedTo
Indicates that one entity is designed, styled, or conceptually based around the subject, motif, or theme represented by another entity.
-
E.
hasThemingDetail
Indicates that something includes or is associated with a specific thematic element, motif, or stylistic detail.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
Created at: April 27, 2026, 2:24 p.m.