Triple

T27636576
Position Surface form Disambiguated ID Type / Status
Subject MatSnackBar E696486 entity
Predicate openFromTemplateSignature P103708 FINISHED
Object openFromTemplate(template: TemplateRef<any>, config?: MatSnackBarConfig) 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: openFromTemplate(template: TemplateRef<any>, config?: MatSnackBarConfig) | Statement: [MatSnackBar, openFromTemplateSignature, openFromTemplate(template: TemplateRef<any>, config?: MatSnackBarConfig)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: openFromTemplateSignature
Context triple: [MatSnackBar, openFromTemplateSignature, openFromTemplate(template: TemplateRef<any>, config?: MatSnackBarConfig)]
  • A. openSignature
    Indicates that an entity formally initiates or signs the opening of something, such as an event, document, or process.
  • B. openedForSignatureBy
    Indicates that one entity has made a document or agreement available for others to sign.
  • C. openedForSignature
    Indicates that an agreement, document, or treaty has been formally made available for eligible parties to sign.
  • D. isTemplateBased chosen
    Indicates that one entity is derived from, structured according to, or instantiated using another entity as a template.
  • E. openedFrom
    Indicates that one entity was initiated, accessed, or launched as a result of an action performed within another entity.
  • 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_69f6359e3d3c81909814e2f0a7fb0ea9 completed May 2, 2026, 5:34 p.m.
PD Predicate disambiguation batch_69f631871c888190bf29466fe4254e51 completed May 2, 2026, 5:16 p.m.
Created at: April 27, 2026, 2:24 p.m.