Triple
T32850820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows 10 version 1803 |
E840245
|
entity |
| Predicate | initialPublicReleaseDate |
P21829
|
FINISHED |
| Object | 2018-04-30 |
—
|
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-04-30 | Statement: [Windows 10 version 1803, initialPublicReleaseDate, 2018-04-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialPublicReleaseDate Context triple: [Windows 10 version 1803, initialPublicReleaseDate, 2018-04-30]
-
A.
firstShortReleaseDate
Indicates the earliest (first) date on which a short version or short-format release of something became publicly available.
-
B.
initialReleaseApprox
Indicates that an entity’s first release or debut occurred around an estimated or approximate point in time rather than on a precisely known date.
-
C.
initialReleaseFor
Indicates that one entity is the first or original release version associated with another entity (such as a work, product, or edition).
-
D.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
E.
originallyReleasedOn
chosen
Indicates the date or platform on which something (such as a work, product, or media item) was first made publicly available.
- 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_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 1, 2026, 1:17 a.m.