Triple
T1654000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows 2000 |
E35755
|
entity |
| Predicate | notableImprovement |
P7339
|
FINISHED |
| Object | improved stability over Windows 9x line |
—
|
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: improved stability over Windows 9x line | Statement: [Windows 2000, notableImprovement, improved stability over Windows 9x line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableImprovement Context triple: [Windows 2000, notableImprovement, improved stability over Windows 9x line]
-
A.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
B.
notableAdvantage
chosen
Indicates that one entity possesses a significant benefit, edge, or favorable quality over another entity or in a given context.
-
C.
notableContribution
Indicates that an entity has made a significant, recognized contribution to another entity, field, work, or endeavor.
-
D.
notablePraise
Indicates that one entity has given significant or distinguished praise or commendation to another entity.
-
E.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.