Triple
T27737940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MatSidenav |
E697573
|
entity |
| Predicate | supportsLayoutPattern |
P109346
|
FINISHED |
| Object | sidenav layout |
—
|
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: sidenav layout | Statement: [MatSidenav, supportsLayoutPattern, sidenav layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLayoutPattern Context triple: [MatSidenav, supportsLayoutPattern, sidenav layout]
-
A.
supportsPatternType
Indicates that one entity is compatible with, or capable of handling, a specified pattern type.
-
B.
hasPatternPlacement
Indicates the spatial or positional arrangement of a pattern relative to or on another entity.
-
C.
layoutSupport
chosen
Indicates that one entity provides or enables structural or spatial arrangement capabilities for another entity.
-
D.
patternSupport
Indicates that one entity provides evidence, validation, or reinforcement for the existence, correctness, or applicability of a particular pattern associated with another entity.
-
E.
hasLayout
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fff328ddc0819080642334a41fcf95 |
completed | May 10, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69fff2e0971c819081aa66f4a6a34b28 |
completed | May 10, 2026, 2:52 a.m. |
Created at: April 27, 2026, 3:13 p.m.