Triple
T27738210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MatSelect |
E697578
|
entity |
| Predicate | styledBy |
P94390
|
FINISHED |
| Object | Angular Material theme |
—
|
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: Angular Material theme | Statement: [MatSelect, styledBy, Angular Material theme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styledBy Context triple: [MatSelect, styledBy, Angular Material theme]
-
A.
styledAs
Indicates that one entity is presented, formatted, or designed in the manner, appearance, or aesthetic of another entity.
-
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.
styleHeldBy
Indicates that a particular style, design, or aesthetic is possessed, used, or embodied by a specific entity.
-
D.
inTheStyleOf
Indicates that one entity is created, performed, or presented in a manner that imitates or closely resembles the characteristic style of another entity.
-
E.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
- 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_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 3:13 p.m.