Triple
T27738326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MatDatepicker |
E697581
|
entity |
| Predicate | hasComponentSelector |
P122530
|
FINISHED |
| Object | mat-datepicker |
—
|
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: mat-datepicker | Statement: [MatDatepicker, hasComponentSelector, mat-datepicker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentSelector Context triple: [MatDatepicker, hasComponentSelector, mat-datepicker]
-
A.
hasSelector
chosen
Indicates that one entity specifies or identifies a particular part, segment, or subset of another entity through a selection mechanism.
-
B.
hasComponentModel
Indicates that an entity includes or is associated with a specific component model as part of its structure or configuration.
-
C.
hasSelectionFor
Indicates that one entity holds or specifies a chosen option, subset, or configuration on behalf of another entity.
-
D.
hasNotableSelector
Indicates that an entity is associated with a particularly important or distinguished selector used to identify or access it.
-
E.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger 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_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: April 27, 2026, 3:13 p.m.