Triple

T27636587
Position Surface form Disambiguated ID Type / Status
Subject MatSnackBar E696486 entity
Predicate designGuidelineSource P81177 FINISHED
Object Google Material Design NE NERFINISHED

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: Google Material Design | Statement: [MatSnackBar, designGuidelineSource, Google Material Design]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designGuidelineSource
Context triple: [MatSnackBar, designGuidelineSource, Google Material Design]
  • A. designCriteria
    Indicates the standards, requirements, or constraints that guide how something should be planned, structured, or created.
  • B. hasGuideline chosen
    Indicates that one entity is governed, informed, or constrained by a rule, standard, or recommended procedure provided by another entity.
  • C. designStandardizedIn
    Indicates that something is designed according to the rules, formats, or specifications defined within a particular standard or standardization framework.
  • D. guidelineNumber
    Indicates the specific numeric identifier assigned to a guideline within a set of rules, standards, or recommendations.
  • E. notableGuideline
    Indicates that something is recognized as an important or especially significant rule, principle, or recommended practice.
  • 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_69f73ae120bc8190bff94d38d7a7a00d completed May 3, 2026, 12:09 p.m.
PD Predicate disambiguation batch_69f73a38d0848190aa5139144b8561c6 completed May 3, 2026, 12:06 p.m.
Created at: April 27, 2026, 2:24 p.m.