Triple
T8363447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Pack 3 |
E197064
|
entity |
| Predicate | isFinalMajorUpdate |
P74013
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Service Pack 3, isFinalMajorUpdate, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFinalMajorUpdate Context triple: [Service Pack 3, isFinalMajorUpdate, true]
-
A.
isLastMajor
Indicates that an entity is the final or most recent significant item or event within a defined sequence or set.
-
B.
isMajorUpgrade
Indicates that one version or change represents a significant, non-trivial upgrade over another in terms of scope, impact, or functionality.
-
C.
latestMajorUpdate
chosen
Indicates the most recent significant update event or version associated with an entity.
-
D.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
E.
isOldestMajor
Indicates that the subject is the oldest entity among a specified group that meets a defined age or maturity threshold.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80768b208190a5f6c9e6cb6e7f30 |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6 p.m.