Triple
T32850796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows 10 Creators Update |
E840244
|
entity |
| Predicate | endOfServiceDateHomePro |
P29802
|
FINISHED |
| Object | 2018-10-09 |
—
|
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: 2018-10-09 | Statement: [Windows 10 Creators Update, endOfServiceDateHomePro, 2018-10-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfServiceDateHomePro Context triple: [Windows 10 Creators Update, endOfServiceDateHomePro, 2018-10-09]
-
A.
holderEndDate
Indicates the date on which an entity’s role as holder of something (e.g., an asset, position, or right) comes to an end.
-
B.
extendedSupportEndDate
chosen
Indicates the date on which an extended support period for something ends.
-
C.
isPrimaryHomeSupportEndFor
Indicates the point in time or condition at which an entity’s role as the main provider of home-based support for another entity ends.
-
D.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
E.
validityPeriodEnd
Indicates the date and time at which a previously valid state, authorization, or condition ceases to be valid.
- 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_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:17 a.m.