Triple
T9689770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackcomb |
E234506
|
entity |
| Predicate | abandonedInFavorOf |
P49004
|
FINISHED |
| Object | more incremental Windows releases |
—
|
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: more incremental Windows releases | Statement: [Blackcomb, abandonedInFavorOf, more incremental Windows releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abandonedInFavorOf Context triple: [Blackcomb, abandonedInFavorOf, more incremental Windows releases]
-
A.
discontinuedInFavorOf
chosen
Indicates that one thing has been stopped, ended, or phased out specifically so it can be replaced by another preferred alternative.
-
B.
abandonedBy
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
-
C.
abandonedIn
Indicates that one entity was left behind or deserted in the location or context specified by another entity.
-
D.
usedInsteadOf
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
-
E.
withdrewInFavorOf
Indicates that one party retracted or gave up its position, claim, or candidacy in support of another party.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d02b20881909d7c0d5d6aaafcb0 |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.