Triple
T27636560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MatSnackBar |
E696486
|
entity |
| Predicate | supportsAccessibilityFeatures |
P181124
|
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, supportsAccessibilityFeatures, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAccessibilityFeatures Context triple: [MatSnackBar, supportsAccessibilityFeatures, true]
-
A.
accessibilityFeatures
Indicates the specific tools, settings, or design elements provided to make something usable or understandable for people with disabilities or diverse access needs.
-
B.
hasAccessibilityVariation
Indicates that one entity differs from another in terms of accessibility features, conditions, or support.
-
C.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
providesAccessibility
Indicates that one entity enables or improves access to another entity, resource, or service, removing or reducing barriers to its use.
-
E.
offersAccessibilityService
chosen
Indicates that an entity provides services or features designed to improve accessibility for people with disabilities or specific access needs.
- 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_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: April 27, 2026, 2:24 p.m.