Triple
T28828564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odyssey (cancelled NT-based project) |
E727979
|
entity |
| Predicate | intendedReleaseType |
P3286
|
FINISHED |
| Object | major Windows NT release |
—
|
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: major Windows NT release | Statement: [Odyssey (cancelled NT-based project), intendedReleaseType, major Windows NT release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedReleaseType Context triple: [Odyssey (cancelled NT-based project), intendedReleaseType, major Windows NT release]
-
A.
intendedForReleaseIn
Indicates that something is planned or scheduled to be made available or launched within a specified context, such as a time, market, or platform.
-
B.
targetRelease
Indicates the specific release or version that an item (such as a feature, fix, or component) is planned or designated to be delivered in.
-
C.
releaseType
chosen
Indicates the kind or category of a release event or version associated with an entity.
-
D.
isReleaseType
Indicates that one entity is classified as a particular type or category of release associated with another entity.
-
E.
appliesToReleaseType
Indicates that a rule, condition, or attribute is specifically relevant or restricted to a particular type of release.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 28, 2026, 6:36 a.m.