Triple
T27636741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MatTooltip |
E696490
|
entity |
| Predicate | stylingMechanism |
P94390
|
FINISHED |
| Object | Angular Material overlay |
—
|
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: Angular Material overlay | Statement: [MatTooltip, stylingMechanism, Angular Material overlay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stylingMechanism Context triple: [MatTooltip, stylingMechanism, Angular Material overlay]
-
A.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
-
B.
stylingEnables
Indicates that one entity provides or activates styling capabilities or visual formatting for another entity.
-
C.
stylingContribution
Indicates a contribution made specifically to the styling, appearance, or visual presentation aspects of something.
-
D.
styleFor
chosen
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
E.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an 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_69f6318d4f2c81908fe25c3dd5d68e94 |
completed | May 2, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:24 p.m.