Triple
T32850764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows 10 Creators Update |
E840244
|
entity |
| Predicate | consumerRolloutStartDate |
P77313
|
FINISHED |
| Object | 2017-04-11 |
—
|
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: 2017-04-11 | Statement: [Windows 10 Creators Update, consumerRolloutStartDate, 2017-04-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consumerRolloutStartDate Context triple: [Windows 10 Creators Update, consumerRolloutStartDate, 2017-04-11]
-
A.
rolloutDate
chosen
Indicates the date on which something (such as a product, feature, or policy) is first introduced or made available for general use.
-
B.
operatorStartDate
Indicates the date on which an operator’s role, activity, or responsibility begins.
-
C.
launchEndDate
Indicates the date on which a launch activity or campaign is completed or comes to an end.
-
D.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
E.
implementedProgramStartDate
Indicates the date on which a particular program was put into effect or began operating in practice.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce786af4819082f159abf7bef62c |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:17 a.m.