Triple
T27636557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MatSnackBar |
E696486
|
entity |
| Predicate | supportsActionButton |
P166402
|
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, supportsActionButton, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsActionButton Context triple: [MatSnackBar, supportsActionButton, true]
-
A.
supportsActionSpace
Indicates that one entity is capable of enabling, handling, or being compatible with a specified action space for operations or behaviors.
-
B.
enabledAction
Indicates that a particular action is permitted, activated, or available to be performed in the given context.
-
C.
supportedAct
Indicates that one entity provided assistance, endorsement, or backing for a particular action or activity performed by another entity.
-
D.
buttonSupport
chosen
Indicates that one entity provides structural or functional support for a button associated with another entity.
-
E.
supportsReach
Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
- 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_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
Created at: April 27, 2026, 2:24 p.m.