Triple
T27738158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MatInput |
E697577
|
entity |
| Predicate | styleGuideline |
P94390
|
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: [MatInput, styleGuideline, Google Material Design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleGuideline Context triple: [MatInput, styleGuideline, Google Material Design]
-
A.
styleRestriction
Indicates a constraint or limitation imposed on the manner, form, or stylistic way in which something may be expressed, presented, or performed.
-
B.
styleFor
chosen
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
C.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
D.
styleOfRule
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
-
E.
styleDescribedAs
Indicates that the manner, aesthetic, or mode of something is characterized or labeled using a particular style description.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 3:13 p.m.